Linked by Thom Holwerda on Thu 12th Apr 2012 08:59 UTC
Internet & Networking I would honestly serve at the altar of the person that did this. Keep the debugging information, but for the love of god, make your email client do something pretty and useful with it.
Permalink for comment 513872
To read all comments associated with this story, please click here.
Member since:


"The thing about FTP, though, is the standard is so simple, and for the vast majority of servers it Just Works. I don't see what needs to change, it's dead simple."

Oddly my experience is different.

I've implemented FTP software, so I appreciate it's simplicity. But in practice I find protocols that span multiple ports to be a bad idea. They cause problems with firewalls and routers, fundamentally requiring very ugly stateful application level gateways to work. Plain FTP usually fails to servers without "passive mode" hacks. Even then it fails between most normal peers. The default ASCII transfer modes can easily cause corruption and doesn't serve much purpose these days.

SFTP is perhaps too complex (being an extension of SSH and all), but network-wise for the most part it just works on all networks that don't have it blocked. It can easily be run behind a NAT on any port one wishes. Obviously it's more secure too.

For me, rsync and sftp more than make up any void left by FTP.

Edited 2012-04-12 15:43 UTC

Reply Parent Score: 6