luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-08-01 15:03:39 +02:00
Code Issues Packages Projects Releases Wiki Activity

Typo.

Browse Source
This commit is contained in:
Tor Lillqvist
2001-01-25 21:19:45 +00:00
parent 8a0df0a71c
commit 20c9c60950
8 changed files with 40 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
ChangeLog
View File

@@ -3,11 +3,11 @@
* 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

10
ChangeLog.pre-2-0
View File

@@ -3,11 +3,11 @@
* 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

10
ChangeLog.pre-2-10
View File

@@ -3,11 +3,11 @@
* 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

10
ChangeLog.pre-2-12
View File

@@ -3,11 +3,11 @@
* 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

10
ChangeLog.pre-2-2
View File

@@ -3,11 +3,11 @@
* 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

10
ChangeLog.pre-2-4
View File

@@ -3,11 +3,11 @@
* 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

10
ChangeLog.pre-2-6
View File

@@ -3,11 +3,11 @@
* 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

10
ChangeLog.pre-2-8
View File

@@ -3,11 +3,11 @@
* 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