Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #3276 > unrolled thread

Re: HTTP over both TCP and UDP

Back to article view | Back to comp.os.linux.networking

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

#3276 — Re: HTTP over both TCP and UDP

Hi every one! I need a little help NS2. I am working on a new AQM technique which treats TCP packets differently from UDP packets. But I don't know how to differentiate TCP from UDP at Routers. I am Using NS2 for the simulations. Your help well be much appreciated and acknowledged. 
my ID is zawarzh@gmail.com

[toc] | [next] | [standalone]

#3277

On 21.2.15 20:16, zawarzh@gmail.com wrote:
> Hi every one! I need a little help NS2. I am working on a new AQM technique which treats TCP packets differently from UDP packets. But I don't know how to differentiate TCP from UDP at Routers. I am Using NS2 for the simulations. Your help well be much appreciated and acknowledged.
> my ID is zawarzh@gmail.com


Time to turn in homeworks at Pakistani universities?

1. There are Wiki pages for Network Simulator 2. I assume that
    you are using it. You should have spelled the name out in full.
    Google for the address of the wiki pages.

2. Please learn the basics of TCP/IP packets. There are different
    transport protocol codes in IP headers for TCP and UDP.

3. Please do not continue a thread which has nothing to do with
    your questions. Now the message header is misleading.

4. There is no idea of reporting your email address. This is a
    public forum, with the responses here, not in mail.

-- 

-TV

[toc] | [prev] | [next] | [standalone]

#3278

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.]




-- 
Mostly harmless...
        -Douglas Adams

[toc] | [prev] | [next] | [standalone]

#3279

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

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.networking

csiph-web