[Libevent-users] cha-ching!

[Kevin Sanders]

On 2/27/07, Toby Douglass <toby.douglass at summerblue.net> wrote:
>
> Sravan Vadlakonda (svadlako) wrote:
> > Toby Douglass wrote:
>
> >> Sorted out weird bug.
> >>
> >> Will do a release this weekend.
>
> > Hi Toby,
> > Can you please say what the bug is that you observed ?
>
> Not really a bug as such - a documentation bug, if you like.
>
> If you call AcceptEx() and specify a non-zero read buffer size,
> GetQueuedCompletionStatus() will NOT return on a connect.  It will only
> return when some data is sent.
>

It's documented properly in my copy of MSDN (dated march 2005);
*dwReceiveDataLength* [in] Number of bytes in *lpOutputBuffer* that will be
used for actual receive data at the beginning of the buffer. This size
should not include the size of the local address of the server, nor the
remote address of the client; they are appended to the output buffer. If *
dwReceiveDataLength* is zero, accepting the connection will not result in a
receive operation. Instead, *AcceptEx* completes as soon as a connection
arrives, without waiting for any data. Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://monkeymail.org/archives/libevent-users/attachments/20070228/f5ed5f2d/attachment.htm