Skip to main content

Timeline for Async Tcpwriter and Reader

Current License: CC BY-SA 4.0

12 events
when toggle format what by license comment
Aug 8, 2019 at 21:56 vote accept Blue
Aug 7, 2019 at 19:12 history edited dfhwze CC BY-SA 4.0
formatting
Aug 7, 2019 at 19:11 answer added dfhwze timeline score: 2
Aug 7, 2019 at 18:15 comment added Stefano d'Antonio If the actions triggered by the completion of one of the two task don't have to be orchestrated, there is no reason to use "WhenAny", you can simply create two separate pipelines with two loops one handling the read and the other handing the payload.
Aug 7, 2019 at 9:41 comment added VisualMelon Since no consensus has been formed, I'll expand on my previous comment: the use of WhenAny means that whichever of the two tasks completes first (ish) will be observed, and the other will be ignored: it will not be cancelled, the task will wait on. For the read, this means losing whatever was read; for GetPayload, this means losing whatever is on top of the queue. This isn't an unlikely event (it will occur every 'cycle' in Run), and I doubt it would pass even a cursory testing.
Aug 7, 2019 at 6:37 comment added Mast @dfhwze Better?
Aug 7, 2019 at 6:37 history edited Mast CC BY-SA 4.0
Rephrased the question to better fit the scope of the site.
Aug 6, 2019 at 17:55 review Close votes
Aug 7, 2019 at 6:37
Aug 6, 2019 at 17:36 history edited dfhwze
tags
Aug 6, 2019 at 17:34 comment added VisualMelon Have you tested this code, and can you show it in use? I ask, because there is a lot that looks wrong with it, and it is missing the 'find handlers'/'dispatch method' bit. It is important that you know how the code works and that it is working as expected before soliciting a review.
Aug 6, 2019 at 17:15 review First posts
Aug 6, 2019 at 17:25
Aug 6, 2019 at 17:11 history asked Blue CC BY-SA 4.0