Access the full text.
Sign up today, get DeepDyve free for 14 days.
References for this paper are not available at this time. We will be adding them shortly, thank you for your patience.
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
netWorker – Association for Computing Machinery
Published: Jun 1, 1998
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.