diff options
author | Bert Belder <bertbelder@gmail.com> | 2010-11-30 17:07:09 +0100 |
---|---|---|
committer | Bert Belder <bertbelder@gmail.com> | 2010-12-20 23:51:29 +0100 |
commit | bd62203d13769a0422078b6b690f2826d2209c63 (patch) | |
tree | 9c2c10053f1aa1dae73c9b3bd195d183dbdef111 /TODO.win32 | |
parent | d66cf5f32cc8bcfa73b32b8a95911cc46c52b6bf (diff) | |
download | node-bd62203d13769a0422078b6b690f2826d2209c63.tar.gz |
Support for non-overlapped sockets
By default windows creates sockets with the WSA_FLAG_OVERLAPPED flag set.
Because child processes don't expect to have overlapped stdio (it never happens)
it won't work with them.
Diffstat (limited to 'TODO.win32')
-rw-r--r-- | TODO.win32 | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/TODO.win32 b/TODO.win32 index 09438698a..b883a8c19 100644 --- a/TODO.win32 +++ b/TODO.win32 @@ -10,7 +10,8 @@ - Child processes
Should not be too hard using CreatePipe, CreateProcessW and GetExitCodeProcess.
- Hooking up the child to a socket is tricky but it can be done (http://www.spinellis.gr/sw/unix/socketpipe/socketpipe-win.c)
+ Hooking up a child process to a file handle can be done; hooking up to a normal socket won't work;
+ we'd need some sort of pump() mechanism.
Waiting for the child to exit is tricky, probably would require a wait thread to wait for the child, then ev_async notify.
How can we distinguish between the exit code and exception number after calling GetExitCodeProcess?
|