Re: Channel response serialization

> Thanks for taking the time to think about this, and hopefully I'm not
being
> too troublesome (or just plain dumb) but there are few people around that
I
> can work through these sorts of issues with.

no. this is a good discussion as it illustrates a lot of issues...

darren pretty much explained the issues in his reply, in particular the
so-called head-of-line problem in trying to move multiple things on one
channel. this leads us to:

[ the web browser example ]

> OK the client could use multiple channels, but then the client is
> effectively dictating how many operations the server can perform in
> parallel.

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!

/mtr