Timeline for Await state async
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 1, 2015 at 15:36 | answer | added | Ewan | timeline score: 0 | |
| Oct 1, 2015 at 6:49 | history | edited | Anders | CC BY-SA 3.0 | added 999 characters in body |
| Oct 1, 2015 at 6:41 | comment | added | Anders | Thats a bug, it should be miliseconds :D | |
| Sep 30, 2015 at 22:31 | comment | added | Doctor Vermilion Wizard | Do you really want to wait for a thousand seconds before failing? | |
| Sep 30, 2015 at 21:26 | comment | added | Kasey Speakman | @RobertHarvey, Task.Delay is like Thread.Sleep except it is non-blocking. See here. It is convenient to use when the containing method is async and therefore await can be used. | |
| Sep 30, 2015 at 20:58 | answer | added | Kasey Speakman | timeline score: 1 | |
| Sep 30, 2015 at 15:12 | comment | added | Robert Harvey | I don't understand this code. What is that await on Task.Delay(100) for? If you're looping while entity == null, haven't you effectively turned it into a blocking call? And you're setting up multiple continuations... I don't see how this code works at all. | |
| Sep 30, 2015 at 13:26 | comment | added | Anders | Did as you asked, only got feedback about code standards, I dont care about that. I want to know about the Task part of the code | |
| Sep 29, 2015 at 13:41 | comment | added | JᴀʏMᴇᴇ | This will probably be well-received on codereview.stackexchange.com | |
| Sep 29, 2015 at 11:05 | history | edited | Anders | CC BY-SA 3.0 | deleted 6 characters in body |
| Sep 29, 2015 at 10:52 | history | asked | Anders | CC BY-SA 3.0 |