On 5 jun 2009, at 14:04, Lloyd Wood wrote:
I.e., what is the benefit of the extra protocols in the middle?
Abstraction. If you write an application that uses network
communications, why would you write low-level socket code in this
day and age? You'd write to a higher level of abstraction and avoid
reinventing the wheel.
Reusing code always seems like a good idea until you actually try to
make it work.
Regardless, a piece of reusable code doesn't automatically make for a
protocol.
(*cough* session layer *cough*)
Sessions with HTTP? Ha.
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?
Do the internals of TCP change when it's running over IPv4 vs IPv6?
Does the interface to upper layers change?
Is answering a question with a question useful?
After a dozen or so messages it's still profoundly unclear to me what
the work would be that we're talking about. But everything that's
mentioned is something relevant to applications, not the internals of
transport protocols.
