Francois PIETTE wrote:
It could work.
A first test seems to confirm that AcceptEx() using
pre-allocated sockets and an I/O completion port is
twice as fast as common Accept(). Only I still do not
get the peer address information thru GetAcceptExSockAddrs :(
On my slow 900 Mhz box I'm now able
Hello,
Today I found AcceptEx() in winsock API
(http://msdn.microsoft.com/library/en-us/winsock/winsock/acceptex_2.asp?frame=true)
and I wonder whether the function might be usefull in a
multi-threaded TWSocketServer. It is capable to accept into an
already existing socket which promises to be
much
effort.
Best Regards,
SubZero
- Original Message -
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Saturday, July 29, 2006 5:30 PM
Subject: [twsocket] AcceptEx() in a MT socket server
Hello,
Today I found AcceptEx() in winsock API
(http
Arno Garrels wrote:
Hello,
Today I found AcceptEx() in winsock API
(http://msdn.microsoft.com/library/en-
us/winsock/winsock/acceptex_2.asp?frame=true) and I wonder whether
the function might be usefull in a multi-threaded TWSocketServer. It
is capable to accept into an already existing
Subject: [twsocket] AcceptEx() in a MT socket server
Hello,
Today I found AcceptEx() in winsock API
(http://msdn.microsoft.com/library/en-us/winsock/winsock/acceptex_2.asp?frame=true)
and I wonder whether the function might be usefull in a
multi-threaded TWSocketServer. It is capable to accept
Francois PIETTE wrote:
assign the sAcceptSocket to property TWSocket.Handle?
That's what Dup() is all about. Dup() assign a socket handle to an
existing TWSocket instance.
Sure, but I was asking because of this note in the docs:
When this operation is successfully completed, sAcceptSocket
assign the sAcceptSocket to property TWSocket.Handle?
That's what Dup() is all about. Dup() assign a socket handle to an
existing TWSocket instance.
Sure, but I was asking because of this note in the docs:
When this operation is successfully completed, sAcceptSocket can be
passed, but to
