Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #3279
| From | Tauno Voipio <tauno.voipio@notused.fi.invalid> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: HTTP over both TCP and UDP |
| Date | 2015-02-23 11:43 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <mcesmd$gn1$1@dont-email.me> (permalink) |
| References | (1 earlier) <87iqks4f38.fsf@com.invalid> <FsLIl.54512$E45.21230@newsfe26.ams2> <b6364b44-6e9b-4fa7-8bfa-599ebc62ef13@googlegroups.com> <mcalhi$2ng$1@dont-email.me> <8e6rrb-rp.ln1@spitzner.org> |
On 23.2.15 10:54, Ralph Spitzner wrote: > Tauno Voipio wrote: > [lots of txt] >> > > Maybe I'm completely retarded, but HTTP _over_ UDP ? > Occurs to me the server would never be able to tell > when it's 'served' a page, unless some ACK's are > implemented, what in turn is just TCP. > > Enlighten me someone on the the use of HTTP > over UDP. > > [i.e. why not just send some <whatever> data > over UDP, don't care whether it's there or not > instead of dealing with headers like > Connection: keep-alive > which is impossible anyway et al.] That was not the only thing wrong in the message. The post did not say anything about HTTP over UDP. It seems to me that the OP is in all over his head about the IP protocol stack - there is a strong homework scent in the whole thing. -- -TV
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: HTTP over both TCP and UDP zawarzh@gmail.com - 2015-02-21 10:16 -0800
Re: HTTP over both TCP and UDP Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2015-02-21 21:16 +0200
Re: HTTP over both TCP and UDP Ralph Spitzner <rasp@spitzner.org> - 2015-02-23 09:54 +0100
Re: HTTP over both TCP and UDP Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2015-02-23 11:43 +0200
csiph-web