- From: Jeffrey Mogul <mogul@pa.dec.com>
- Date: Mon, 08 May 95 15:05:07 MDT
- To: Ned Freed <NED@sigurd.innosoft.com>
- Cc: jag@scndprsn.eng.sun.com, masinter@parc.xerox.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Actually, I see it the other way around, with byte stuffing being
the hack and unique boundaries as the cleanest way to do it. I also
disagree about it being simpler -- byte stuffing requires that you
diddle the stream as it is sent, which complicates your inner
processing loop where you spend your time. Boundaries keep that
loop nice and simple.
I agree. Consider what happens as the size of the user population
scales. So you have 100 million users, all with mostly-idle Pentiums
on their desks, beating on your server (probably a multiprocessor
Alpha :-) ).
So, do you want that server to be byte-stuffing all the data streams?
Or would you rather leave the burden to the clients? I know what
I would want to do.
-Jeff
Received on Monday, 8 May 1995 16:48:56 UTC