* giowin32.c: Socket support rewritten. It was utterly broken, and
untested in fact. We still do use a thread for each socket being
watched, but instead of blocking in recv() (which of course was
- plain stupid for sockets being liste()ed on), we block in
- select(). The read method for sockets calls recv(). It is now
- possible for the application to call accept(), recv() or send() in
- the callback, just like on Unix. Tested with code kindly provided
- by Andrew Lanoix.
+ plain stupid for sockets being listen()ed on in a server-type
+ application), we block in select(). The read method for sockets
+ calls recv(). It is now possible for the application to call
+ accept(), recv() or send() in the callback, just like on
+ Unix. Tested with code kindly provided by Andrew Lanoix.
Rename g_io_channel_win32_new_stream_socket() to
g_io_channel_win32_new_socket() as it isn't restricted to stream
* giowin32.c: Socket support rewritten. It was utterly broken, and
untested in fact. We still do use a thread for each socket being
watched, but instead of blocking in recv() (which of course was
- plain stupid for sockets being liste()ed on), we block in
- select(). The read method for sockets calls recv(). It is now
- possible for the application to call accept(), recv() or send() in
- the callback, just like on Unix. Tested with code kindly provided
- by Andrew Lanoix.
+ plain stupid for sockets being listen()ed on in a server-type
+ application), we block in select(). The read method for sockets
+ calls recv(). It is now possible for the application to call
+ accept(), recv() or send() in the callback, just like on
+ Unix. Tested with code kindly provided by Andrew Lanoix.
Rename g_io_channel_win32_new_stream_socket() to
g_io_channel_win32_new_socket() as it isn't restricted to stream
* giowin32.c: Socket support rewritten. It was utterly broken, and
untested in fact. We still do use a thread for each socket being
watched, but instead of blocking in recv() (which of course was
- plain stupid for sockets being liste()ed on), we block in
- select(). The read method for sockets calls recv(). It is now
- possible for the application to call accept(), recv() or send() in
- the callback, just like on Unix. Tested with code kindly provided
- by Andrew Lanoix.
+ plain stupid for sockets being listen()ed on in a server-type
+ application), we block in select(). The read method for sockets
+ calls recv(). It is now possible for the application to call
+ accept(), recv() or send() in the callback, just like on
+ Unix. Tested with code kindly provided by Andrew Lanoix.
Rename g_io_channel_win32_new_stream_socket() to
g_io_channel_win32_new_socket() as it isn't restricted to stream
* giowin32.c: Socket support rewritten. It was utterly broken, and
untested in fact. We still do use a thread for each socket being
watched, but instead of blocking in recv() (which of course was
- plain stupid for sockets being liste()ed on), we block in
- select(). The read method for sockets calls recv(). It is now
- possible for the application to call accept(), recv() or send() in
- the callback, just like on Unix. Tested with code kindly provided
- by Andrew Lanoix.
+ plain stupid for sockets being listen()ed on in a server-type
+ application), we block in select(). The read method for sockets
+ calls recv(). It is now possible for the application to call
+ accept(), recv() or send() in the callback, just like on
+ Unix. Tested with code kindly provided by Andrew Lanoix.
Rename g_io_channel_win32_new_stream_socket() to
g_io_channel_win32_new_socket() as it isn't restricted to stream
* giowin32.c: Socket support rewritten. It was utterly broken, and
untested in fact. We still do use a thread for each socket being
watched, but instead of blocking in recv() (which of course was
- plain stupid for sockets being liste()ed on), we block in
- select(). The read method for sockets calls recv(). It is now
- possible for the application to call accept(), recv() or send() in
- the callback, just like on Unix. Tested with code kindly provided
- by Andrew Lanoix.
+ plain stupid for sockets being listen()ed on in a server-type
+ application), we block in select(). The read method for sockets
+ calls recv(). It is now possible for the application to call
+ accept(), recv() or send() in the callback, just like on
+ Unix. Tested with code kindly provided by Andrew Lanoix.
Rename g_io_channel_win32_new_stream_socket() to
g_io_channel_win32_new_socket() as it isn't restricted to stream
* giowin32.c: Socket support rewritten. It was utterly broken, and
untested in fact. We still do use a thread for each socket being
watched, but instead of blocking in recv() (which of course was
- plain stupid for sockets being liste()ed on), we block in
- select(). The read method for sockets calls recv(). It is now
- possible for the application to call accept(), recv() or send() in
- the callback, just like on Unix. Tested with code kindly provided
- by Andrew Lanoix.
+ plain stupid for sockets being listen()ed on in a server-type
+ application), we block in select(). The read method for sockets
+ calls recv(). It is now possible for the application to call
+ accept(), recv() or send() in the callback, just like on
+ Unix. Tested with code kindly provided by Andrew Lanoix.
Rename g_io_channel_win32_new_stream_socket() to
g_io_channel_win32_new_socket() as it isn't restricted to stream
* giowin32.c: Socket support rewritten. It was utterly broken, and
untested in fact. We still do use a thread for each socket being
watched, but instead of blocking in recv() (which of course was
- plain stupid for sockets being liste()ed on), we block in
- select(). The read method for sockets calls recv(). It is now
- possible for the application to call accept(), recv() or send() in
- the callback, just like on Unix. Tested with code kindly provided
- by Andrew Lanoix.
+ plain stupid for sockets being listen()ed on in a server-type
+ application), we block in select(). The read method for sockets
+ calls recv(). It is now possible for the application to call
+ accept(), recv() or send() in the callback, just like on
+ Unix. Tested with code kindly provided by Andrew Lanoix.
Rename g_io_channel_win32_new_stream_socket() to
g_io_channel_win32_new_socket() as it isn't restricted to stream
* giowin32.c: Socket support rewritten. It was utterly broken, and
untested in fact. We still do use a thread for each socket being
watched, but instead of blocking in recv() (which of course was
- plain stupid for sockets being liste()ed on), we block in
- select(). The read method for sockets calls recv(). It is now
- possible for the application to call accept(), recv() or send() in
- the callback, just like on Unix. Tested with code kindly provided
- by Andrew Lanoix.
+ plain stupid for sockets being listen()ed on in a server-type
+ application), we block in select(). The read method for sockets
+ calls recv(). It is now possible for the application to call
+ accept(), recv() or send() in the callback, just like on
+ Unix. Tested with code kindly provided by Andrew Lanoix.
Rename g_io_channel_win32_new_stream_socket() to
g_io_channel_win32_new_socket() as it isn't restricted to stream
projects / platform / upstream / glib.git / commitdiff