Re: Channel response serialization

> > the whole point here is that client should be using multiple channels
> > because tit should want to manage the html and the gifs with different
> > priorities!
> 
> Yes. So it uses one channel for HTML and one channel for all of the GIFs it
> wants to download in parallel. Or is that what you're saying?

Not necessarily; I think Marshall was suggesting that with a set of
indistinguishable channels, it uses some subset (say, one) for
retrieving HTML, and another subset (as many as it wishes, or thinks
it can handle in parallel), for retrieving the GIFs.  It can always
hold onto more channels than it is using at any given time, as
channels are lightweight and cheap.

Consider this to be the same way existing browsers manage multiple
connections, except that the resource cost is not as steep.

--Jered