Re: OTSndOrderlyDisconnect
Re: OTSndOrderlyDisconnect
- Subject: Re: OTSndOrderlyDisconnect
- From: Jason Linhart <email@hidden>
- Date: Wed, 9 Jul 2003 09:57:27 -0400
On 7/9/03 4:48 AM Quinn (email@hidden) wrote:
>
That depends on what protocol the servers speak. For example, the
>
HTTP protocol specifies the following sequence.
>
>
1. client opens connection
>
2. client sends request
>
3. server sends response
>
4. server starts disconnect
>
5. client confirms disconnect
>
>
If you're implementing HTTP, you have to follow this sequence.
>
>
[It would be a lot nicer to busy HTTP servers if the specification
>
had required the following sequence.
>
>
1. client opens connection
>
2. client sends request
>
3. client starts disconnect
>
4. server sends response
>
5. server confirms disconnect
>
>
However, that's not how it works.]
Some of the major browsers use the second sequence, and all of the
servers I have seen support it, even if it is not allowed by the formal
spec.
Jason
-----------------
email@hidden
-----------------
Dr. Seuss books . . . can be read and enjoyed on several levels. For
example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed
as a searing indictment of the narrow-minded binary counting system.
-- Peter van der Linden, Expert C Programming, Deep C Secrets
_______________________________________________
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.