Hi Josh,
thanks for the confirmation.
It was interesting to note that there was a "connected" event but no
"connecting". Not a surprise for an accept socket, though.
I guess the call to the connect-in function comes on the listen socket,
which I don't see. Given that, is there any way to find the remote
address which connected?
Thanks.....Peter
>
>That is a very likely scenario. In addition to getting a listen event
>on the socket listening for incoming connections (which you missed by
>not being registered at the time the socket was created), you will
>get connected events for new sockets created for inbound connections
>to that original listening socket.
>
>-josh
>
>On Dec 12, 2005, at 5:04 AM, Peter Lovell wrote:
>
>> Good morning folks,
>> I'd just like to verify that a particular event sequence I see is
>> actually what I think it is.
>>
>> What I see is that my attach function is called for a TCP socket
>> and the
>> next thing is a call to my notify function for sock_evt_connected.
>>
>> What I think is that this is a new socket created for an incoming
>> connection as part of the "accept" processing. I didn't see the listen
>> or any of the things related to the incoming connect because the
>> listening socket was created before my kext is started, so I'm not
>> registered on that listening socket.
>>
>> Thanks.....Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macnetworkprog/email@hidden
This email sent to email@hidden
