Message135544
Ok, here's a patch for the new approach.
CancelIoEx is loaded dynamically and, if unavailable, CancelIo is used instead. I take care to cancel or complete the I/O in the same method call where it is initiated, meaning there's no thread-specificity issues.
(of course, all this is a lot of code just to have the desired WaitForMultipleObjects() semantics on a named pipe. Thank you, Windows) |
|
Date |
User |
Action |
Args |
2011-05-08 21:28:25 | pitrou | set | recipients:
+ pitrou, bquinlan, vstinner, jnoller, hongqn, brian.curtin, asksol, vlasovskikh, gdb, Albert.Strasheim, aljungberg, gkcn |
2011-05-08 21:28:23 | pitrou | set | messageid: <1304890103.08.0.698383464249.issue9205@psf.upfronthosting.co.za> |
2011-05-08 21:28:22 | pitrou | link | issue9205 messages |
2011-05-08 21:28:22 | pitrou | create | |
|