➜

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 r.david.murray
Recipients amaury.forgeotdarc, beazley, dabeaz, flox, gregory.p.smith, loewis, ned.deily, pitrou, r.david.murray, rosslagerwall, roysmith
Date 2011-10-20.20:40:42
SpamBayes Score 0.00014402253
Marked as misclassified No
Message-id <1319143243.87.0.73842122466.issue7322@psf.upfronthosting.co.za>
In-reply-to
Content 
Your suggestion sounds good to me.

I still think that it is a common failure mode in a client server transaction for the server to fail to send a (complete) line that the client is expecting, and vice versa, requiring a timeout, but not necessarily a "restart from scratch".  Often the client/server protocol has a useful checkpoint to restart from short of start from scratch.  In the case of many protocols, that would be "client issues a new command".
History
Date User Action Args
2011-10-20 20:40:44r.david.murraysetrecipients: + r.david.murray, loewis, beazley, gregory.p.smith, amaury.forgeotdarc, roysmith, pitrou, ned.deily, flox, dabeaz, rosslagerwall
2011-10-20 20:40:43r.david.murraysetmessageid: <1319143243.87.0.73842122466.issue7322@psf.upfronthosting.co.za>
2011-10-20 20:40:43r.david.murraylinkissue7322 messages
2011-10-20 20:40:42r.david.murraycreate