Hi
Can any one explain me how HTTP related to TCP?
Thanks
Somak

On Oct 15, 4:31 pm, somak...@gmail.com wrote:
> Hi
> Can any one explain me how HTTP related to TCP?


Sure, not a problem at all. But you should really do your own
homework, you'll learn much more that way.

Now if, once you do some research, have some questions about any
specifics, fire away...

somaks.b@gmail.com wrote:
> Hi
> Can any one explain me how HTTP related to TCP?
> Thanks
> Somak
>

When is the homework or takehome exam due ?

Why don't you start by telling us what you think the answer might be,
and what references you have checked so far?

In article <13h7uosr3fro19c@corp.supernews.com>,
FLY135 <fly_135(at hot not not)mail.com> wrote:

>TCP can be be used by many protocols. However, HTTP must use TCP.

Why couldn't HTTP run over TP4 instead of TCP, except perhaps for
decoding some flavors of URI? Page 8 of RFC 1945 says

On the Internet, HTTP communication generally takes place over TCP/IP
connections. The default port is TCP 80 [15], but other ports can be
used. This does not preclude HTTP from being implemented on top of
any other protocol on the Internet, or on other networks. HTTP only
presumes a reliable transport; any protocol that provides such
guarantees can be used, and the mapping of the HTTP/1.0 request and
response structures onto the transport data units of the protocol in
question is outside the scope of this specification.


Or if the point was to say that one can't run TCP over HTTP, why couldn't
one tunnel IP and so TCP over HTTP? It sounds easier than tunneling
IP over DNS.


Vernon Schryver vjs@rhyolite.com

On Oct 15, 7:02 pm, v...@calcite.rhyolite.com (Vernon Schryver) wrote:
> Or if the point was to say that one can't run TCP over HTTP, why couldn't
> one tunnel IP and so TCP over HTTP? It sounds easier than tunneling
> IP over DNS.


See RFC 3093.

<somaks.b@gmail.com> wrote in message
news:1192483869.734564.193230@t8g2000prg.googlegro ups.com...
> Hi
> Can any one explain me how HTTP related to TCP?

TCP is a protocol (algorithm) that provides for transmission of data by
packetization. It uses various mechanisms such as sequence numbers,
acknowledgement, and resend for reliable delivery. HTTP is another protocol
that relies on TCP to get the data to the end point. That is the extent of
the relationship. HTTP is higher on the OSI model stack than TCP.

TCP can be be used by many protocols. However, HTTP must use TCP. You can
make up your own protocols that use TCP, and they could be useful. There
are many protocols that use TCP. But you cannot make up a protocol for HTTP
to use other than TCP. Because it could not talk to anything. Except in
your closed system.

On Oct 15, 7:02 pm, v...@calcite.rhyolite.com (Vernon Schryver) wrote:
> In article <13h7uosr3fro...@corp.supernews.com>,
> FLY135 <fly_135(at hot not not)mail.com> wrote:
>
> >TCP can be be used by many protocols. However, HTTP must use TCP.
>
> Why couldn't HTTP run over TP4 instead of TCP, except perhaps for
> decoding some flavors of URI? Page 8 of RFC 1945 says
>
> On the Internet, HTTP communication generally takes place over TCP/IP
> connections. The default port is TCP 80 [15], but other ports can be
> used. This does not preclude HTTP from being implemented on top of
> any other protocol on the Internet, or on other networks. HTTP only
> presumes a reliable transport; any protocol that provides such
> guarantees can be used, and the mapping of the HTTP/1.0 request and
> response structures onto the transport data units of the protocol in
> question is outside the scope of this specification.
>
> Or if the point was to say that one can't run TCP over HTTP, why couldn't
> one tunnel IP and so TCP over HTTP? It sounds easier than tunneling
> IP over DNS.

The point was that you wouldn't be generally compatible with anything
else other than your closed system. But yes, there may be other
protocols that HTTP can run on that are standard.

FLY135