Hi,
Just checked in a fix:
IPv6 MacOS - Bugfix in main event loop.
Accept events were lost when a connection request still pending in the listen
backlog queue was closed by the peer. Fixed by use of level triggered events
and disable/enable the filter as required (similar as read events as well
Arno Garrels wrote:
> state. Looks like _if a client closes a socket when the
> connection is still in the listen backlog queue no event fires :(
Problem/reason found :)
When kqueue fires an accept-event its Data member contains the
number of connect requests waiting in the listen backlog queue.
Arno Garrels wrote:
> Arno Garrels wrote:
>> Hi,
>>
>> I should have tested more carefully, sorry for that.
>> After some stress tests with the webserver for MacOS
>> I hit a bug today that I do not understand.
>> Once in some state Accept() returns a socket handle
>> with a port number that doesn
Arno Garrels wrote:
> Hi,
>
> I should have tested more carefully, sorry for that.
> After some stress tests with the webserver for MacOS
> I hit a bug today that I do not understand.
> Once in some state Accept() returns a socket handle
> with a port number that doesn't match the port number of
>
Hi,
I should have tested more carefully, sorry for that.
After some stress tests with the webserver for MacOS
I hit a bug today that I do not understand.
Once in some state Accept() returns a socket handle
with a port number that doesn't match the port number of
the connecting socket.
Anybody a
