🚀 go-pugleaf

In article <1992Sep24.183440.2719@advtech.uswest.com>, huntting@advtech.uswest.com (Brad Huntting) writes:
- In article <1992Sep22.202619.3942@cc.ic.ac.uk> cmaae47@cc.ic.ac.uk (me):
- > compression "belongs" into layer 6 (presentation)
.....
- Putting compression above the network layer is a mistake.  I dought
- that compression would help speed up a large file transfer over FDDI.

Only if the file has not been encrypted. Thus you may catch a lot now,
but soon you will have no more benefit from compression, as most network
traffic will become encrypted.

- The complexity you would add to each application would be expensive
- enough that noone would use it.

That's why it should be in the presentation layer, so that no application
needs to bother with compression.

- You can deal with bad interactive response by devising a good heuristic
- method to determine the nature of the trafic over the line.

Actually, no, heuristics don't help, devolving response management to 
somewhere near the user would. Unfortuanately (misguided) software develoment
has put response (for screen editors) as far as possible away from the user,
but that is another battle.

                                    Thomas
--
*** This is the operative statement, all previous statements are inoperative.
*   email: cmaae47 @ cc.ic.ac.uk (Thomas Sippel - Dau) (uk.ac.ic.cc on Janet)
*   voice: +44 71 589 5111 x4937 or 4934 (day), or +44 71 823 9497 (fax)
*   snail: Imperial College of Science, Technology and Medicine
*   The Center for Computing Services, Kensington SW7 2BX, Great Britain