This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xdegaye
Recipients giampaolo.rodola, josiahcarlson, neologix, stutzbach, terry.reedy, vstinner, xdegaye
Date 2011-10-27.18:37:30
SpamBayes Score 5.6620485e-07
Marked as misclassified No
Message-id <1319740651.32.0.315486895161.issue5661@psf.upfronthosting.co.za>
In-reply-to
Content
> Did you try with the current branches?

Yes, the test is pass against the current default and 2.7 branches.
One must remove EPIPE from the asyncore._DISCONNECTED frozenset to
make the test to fail.


> Yes, see RFC1122 section 4.2.2.13:
> """
>             A host MAY implement a "half-duplex" TCP close sequence, so
>             that an application that has called CLOSE cannot continue to
>             read data from the connection.  If such a host issues a
>             CLOSE call while received data is still pending in TCP, or
>             if new data is received after CLOSE is called, its TCP
>             SHOULD send a RST to show that data was lost.
> """

Thanks for the pointer. Note that the "half-duplex" FIN-ACK-RESET
occurs when all received data has been read, and a single RESET is
sent when received data is still pending in the stream.
History
Date User Action Args
2011-10-27 18:37:31xdegayesetrecipients: + xdegaye, terry.reedy, josiahcarlson, vstinner, giampaolo.rodola, stutzbach, neologix
2011-10-27 18:37:31xdegayesetmessageid: <1319740651.32.0.315486895161.issue5661@psf.upfronthosting.co.za>
2011-10-27 18:37:30xdegayelinkissue5661 messages
2011-10-27 18:37:30xdegayecreate