Re: Endpoint reuse
Re: Endpoint reuse
- Subject: Re: Endpoint reuse
- From: Mark Thomas <email@hidden>
- Date: Thu, 06 Mar 2003 12:26:25 +0000
- Organization: Coderus Ltd
So I guess, what you saying is that I have to do OTAccept regardless if I
want the connection or not :-(, so I can get hold of the endpoint/port which
the kernel gave the connection, and then do a OTSndDisconnect, to break the
connection, and then on the client side pick up that the connection is gone.
Does that sounds right ??.
Thanks
Mark.
>
Message: 3
>
Date: Wed, 5 Mar 2003 17:06:43 +0000
>
To: Macintosh Network Programming <email@hidden>
>
From: Quinn <email@hidden>
>
Subject: Re: Endpoint reuse
>
>
At 12:47 +0000 5/3/03, Mark Thomas wrote:
>
> Now on the client side I do :-
>
>
>
> Err = OTConnect( ... )
>
>
>
> its returns noErr, which is strange, as I thought its rejected, and then if
>
> I check the endpoint's state its 5 (data transfer mode), so I guess it
>
> wasn't rejected.
>
>
This behaviour is inherent in the mismatch of semantics between OSI
>
networking and TCP. In OSI networking, which is what OT's XTI API
>
was designed for, the application can decide whether to reject or
>
accept an incoming connection. In TCP, the kernel always accepts or
>
rejects the connection attempt, depending on whether the port is
>
bound. So, because the port is bound for listening, the remote
>
peer's OTConnect succeeds, and the caller returns immediately.
>
However, the server's rejection of the connection (via
>
OTSndDisconnect) will cause the connection to then break. This is
>
described in moredetail in DTS Q&A NW 24.
>
>
<http://developer.apple.com/qa/nw/nw24.html>
>
>
S+E
>
--
>
Quinn "The Eskimo!" <http://www.apple.com/developer/>
>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.