Re: Should Web Services be served by a different HTTP n+1?

I mean, we have spent a great deal of effort over the last couple of
decades to minimize state in general, in TCP TCBs in particular, and
so on.  We've done that for a reason.

Also, there had better be a bound to stateful compression state size,
and therefore, deterministic synchronization or a synchronization
protocol (which would... add latency).

It's not at all obvious to me that stateful compression is a good
idea.  It is clear that only stateful compression can do something
about values that get repeated a lot, like cookies and URL prefixes,
but I'm not sure that's worth the trouble.

Nico
--

Received on Thursday, 24 January 2013 23:02:18 UTC