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 giampaolo.rodola
Recipients exarkun, giampaolo.rodola, loewis, nagle, pitrou
Date 2010-10-27.10:26:26
SpamBayes Score 0.00010621826
Marked as misclassified No
Message-id <1288175193.95.0.109062787396.issue10202@psf.upfronthosting.co.za>
In-reply-to
Content
> Proper behavior for ftplib when sending is to send all desired data, 
> then call "sock.shutdown(socket.SHUT_RDWR)".  This indicates that no 
> more data will be sent, and blocks until the receiver has acknowledged 
> all their data. 

I'm not sure about this. Such a requirement should be respected by both peers and AFAICR there's no FTP-related RFC which explicitly states that shutdown() should be used.

http://www.rfc-archive.org/getrfc.php?rfc=4217 chapter 12.4 should reflect the same use case we're talking about: a client sending a file (STOR).
In the example only close() is used, which perhaps should lead this discussion to question whether socket's close() method is implemented properly, as your linux man quote suggests.
History
Date User Action Args
2010-10-27 10:26:34giampaolo.rodolasetrecipients: + giampaolo.rodola, loewis, exarkun, nagle, pitrou
2010-10-27 10:26:33giampaolo.rodolasetmessageid: <1288175193.95.0.109062787396.issue10202@psf.upfronthosting.co.za>
2010-10-27 10:26:27giampaolo.rodolalinkissue10202 messages
2010-10-27 10:26:26giampaolo.rodolacreate