>
> These are two different things for different purposes, the application
> performance and the network performance.
>
> HTTP is at the application layer and can send some information before
> others assuming the receiving application can make good use of it
> without waiting for all of it.
>
> TCP is at the transport layer and can send some information in
> separate packets assuming the overall network will work better with a
> steady flow of similar, small-sized units of information. Then it will
> reassemble them on the other end so you don't have to.
Yes I know all that ;-). I was trying to nail down what the fundamental
difference between a transfer and transport protocol is. The best I've
seen so far is "its the layers in the OSI ref model stupid" .. which is
hardly satisfying .. at least to me.
Anyway, thanks for the responses; I didn't really want to have a long
thread on this- I was looking for an enlightened one to give a solid,
simple definition but that does not appear to be forthcoming.
Sanjiva.
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
