Timeline for Writing a TCP protocol or use HTTP for file transfer?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2013 at 22:11 | audit | Suggested edits | |||
| Feb 26, 2013 at 22:12 | |||||
| Feb 25, 2013 at 19:04 | comment | added | Dave Hillier | As someone who has worked on games I can tell you that they do use HTTP, when appropriate. | |
| Feb 25, 2013 at 16:49 | comment | added | Daniel | @DaveHillier, since I'm developing both client and server, using TCP I can omit the redundant headers, and simply transfer raw bytes. Besides, I can notify client B that it's about to receive a file instantly as client A sends it. Not sure how to do that using HTTP. But obviously you are right, that HTTP rides on top of TCP so the difference will probably be unnoticeable. The question is, why, for instance, game developers use sockets then, and don't simply transfer data using HTTP or some other application layer protocol? | |
| Feb 25, 2013 at 16:37 | comment | added | mouviciel | And what about NFS or its siblings? | |
| Feb 25, 2013 at 7:43 | vote | accept | Daniel | ||
| Feb 25, 2013 at 7:40 | vote | accept | Daniel | ||
| Feb 25, 2013 at 7:41 | |||||
| Feb 25, 2013 at 1:56 | comment | added | yannis | Take John R. Strohm's advice and go with FTP. It's not as illustrious as any other solution to your problem, but that doesn't mean it's not a correct (and probably the best) solution. KISS. | |
| Feb 24, 2013 at 22:12 | comment | added | Dave Hillier | Again, what is it that you think makes TCP that much faster than HTTP, or some other application level protocol? | |
| Feb 24, 2013 at 21:12 | answer | added | Cosmin Prund | timeline score: 1 | |
| Feb 24, 2013 at 18:02 | comment | added | Daniel | @DaveHillier, 1. This is a real problem since I don't want to waste my time on experimenting different protocols. 2. I wasn't comparing HTTP to TCP, I was just asking, which one would be better if I want the files to arrive as quickly as possible from client to client, considering that HTTP is stateless, whereas a TCP socket can be stateful. | |
| Feb 24, 2013 at 16:40 | comment | added | Dave Hillier | Why would your protocol be more responsive than HTTP? TCP and HTTP is an apples and oranges comparison. Or a transport and application layer comparison. There are many other alternatives for protocols in the application layer. This isnt a real problem you have. Go do one of the options that you have, usually the higher level one. When you have a problem post here. | |
| Feb 24, 2013 at 16:30 | answer | added | John R. Strohm | timeline score: 9 | |
| Feb 24, 2013 at 14:56 | answer | added | Jim Nutt | timeline score: 3 | |
| Feb 24, 2013 at 8:53 | history | edited | Martijn Pieters | CC BY-SA 3.0 |
deleted 9 characters in body; edited title
|
| Feb 24, 2013 at 8:37 | review | First posts | |||
| Feb 24, 2013 at 8:53 | |||||
| Feb 24, 2013 at 8:18 | history | asked | Daniel | CC BY-SA 3.0 |