| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
| |
driver to move the handling of the socket event window in a
separate thread. It also turned out that Win95 & Win98 were, in
some cases, getting multiple FD_ACCEPTs but only handling one.
Added a count for the FD_ACCEPT to take care of this. Tested on
NT4 SP3, NT4 SP4, Win95, and Win98.
[Bug: 2178 2256 2259 2329 2323 2355]
|
| |
|
|
|
|
| |
because of serious problems with the new driver. Basically no
incoming socket connections would be reported to a server port.
The 8.1.1 code needs to be redesigned and fixed correctly.
|
| |
|
|
|
|
| |
win/tclWinSock.c: Fixed hang in WinNT socket driver, now wakes up
the socket thread to check for events that didn't
trigger the WSAEvent.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- Mac changes for final release
- Minor fixes to tools configure file
* win/tclWinSock.c: Apply patch to allow write access to a socket
if FD_WRITE is sent but FD_CONNECT is not. Some strange problem
with either Win32 or a socket driver. [Bug: 1664 1776]
|
| | |
|
| |
|
|
|
|
|
| |
* win/tclWinSock.c:
* doc/socket.n: Applied Gordon Chaffee's patch to handle failures
during asynchronous socket connection operations. This adds a new
"-error" fconfgure option to socket channels. [Bug: 893]
|
| |
|
|
|
| |
sockets so they are inheritable by default. Turn off this bit so
sockets aren't kept open by exec'ed processes. [Bug: 892]
|
| | |
|
| |
|
|
| |
changed to completely drain the socket window before checking any state
|
| |
|
