On 4 jun 2009, at 18:24, Eddy, Wesley M. (GRC-MS00)[Verizon] wrote:
The distinction between these two layers (transport and application) is quite blurry when it comes to "applications" that end up being used as middleware for other applications. Application protocols stacked on other application protocols 3 or 4 deep is no longer uncommon,
Why is this a good idea, though? If a packet gets lost doesn't TCP retransmit? If data doesn't fit in one packet, doesn't TCP segment? If you prick it, doesn't TCP bleed?
I.e., what is the benefit of the extra protocols in the middle?
But back to the point on this thread ... considering that the proposal is to use HTTP to provide an interface for transport services, and not to extend HTTP as it also exists as a top-of-the-stack application, it is definitely more applicable to the TSV area than the APP area.
Can you explain a bit more? HTTP runs over a "real" transport protocol. I assume this won't change. Do the internals of HTTP change? Or its interface to upper layers?
