Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

And nothing to watch: bad protocols, good users: in praise of evolvable systems

And nothing to watch: bad protocols, good users: in praise of evolvable systems and nothing to watch BAD PROTOCOLS, GOOD USERS: IN PRAISE OF E V O L VA B L E S Y S T E M S B Y C L AY S H I R K Y Why something as poorly designed as the Web became The Next Big Thing, and what that means for the future. If it were April Fool ™s Day, the Net ™s only official holiday, and you wanted to design a œNovelty Protocol  to slip by the Internet Engineering Task Force as a joke, it might look something like the Web: " The server would use neither a persistent connection nor a store-and-forward model, thus giving it all the worst features of both telnet and e-mail. " The server ™s primary method of extensibility would require spawning external processes, thus ensuring both security risks and unpredictable load. " The server would have no built-in mechanism for gracefully apportioning resources, refusing or delaying heavy traffic, or load-balancing. It would, however, be relatively easy to crash. " Multiple files traveling together from one server to one client would each incur the entire overhead of a new session call. " The hypertext model would ignore http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png netWorker Association for Computing Machinery

And nothing to watch: bad protocols, good users: in praise of evolvable systems

netWorker , Volume 2 (3) – Jun 1, 1998

Loading next page...
 
/lp/association-for-computing-machinery/and-nothing-to-watch-bad-protocols-good-users-in-praise-of-evolvable-BoA9geOaUl

References

References for this paper are not available at this time. We will be adding them shortly, thank you for your patience.

Publisher
Association for Computing Machinery
Copyright
Copyright © 1998 by ACM Inc.
ISSN
1091-3556
DOI
10.1145/280506.280518
Publisher site
See Article on Publisher Site

Abstract

and nothing to watch BAD PROTOCOLS, GOOD USERS: IN PRAISE OF E V O L VA B L E S Y S T E M S B Y C L AY S H I R K Y Why something as poorly designed as the Web became The Next Big Thing, and what that means for the future. If it were April Fool ™s Day, the Net ™s only official holiday, and you wanted to design a œNovelty Protocol  to slip by the Internet Engineering Task Force as a joke, it might look something like the Web: " The server would use neither a persistent connection nor a store-and-forward model, thus giving it all the worst features of both telnet and e-mail. " The server ™s primary method of extensibility would require spawning external processes, thus ensuring both security risks and unpredictable load. " The server would have no built-in mechanism for gracefully apportioning resources, refusing or delaying heavy traffic, or load-balancing. It would, however, be relatively easy to crash. " Multiple files traveling together from one server to one client would each incur the entire overhead of a new session call. " The hypertext model would ignore

Journal

netWorkerAssociation for Computing Machinery

Published: Jun 1, 1998

There are no references for this article.