Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Whole solution and experience is different, even if some point uploading file by bytes over TCP is similar. HTTP server itself isn't solution. You need code implementing upload functionality, probably support for uploading many files at once and tracking progress. Now you client uses javascript and that client is remote, you need to "download" it from HTTP server. FTP client is small, local and don't have much overhead, HTTP with its stateless form needs headers retransmitted with every request.


That’s all well and good, and has nothing to do with Chromium keeping ftp support.


Indeed, but your question wasn't about Chromium ftp support. Note, I am not lazylizard, so I don't really know, what he meant by "Ftp is fast", but I have my own thoughs and general dislike to webify everything on internet.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: