Document
World Wide Web
The WorldWideWeb (W3) is a wide-area hypermedia information retrieval initiative aiming to give universal access to a large universe of documents. Everything there is online about W3 is linked directly or indirectly to this document, including an executive summary of the project, Mailing lists , Policy , November's W3 news , Frequently Asked Questions .
What's out there?
Pointers to the world's online information, subjects , W3 servers, etc.
Help
on the browser you are using
Software Products
A list of W3 project components and their current state. (e.g. Line Mode ,X11 Viola , NeXTStep , Servers , Tools , Mail robot , Library )
Technical
Details of protocols, formats, program internals etc
Bibliography
Paper documentation on W3 and references.
People
A list of some people involved in the project.
History
A summary of the history of the project.
How can I help ?
If you would like to support the web..
Getting code
Getting the code by anonymous FTP , etc.
===== Assignment 2 =====
Had to add this to render the dashes ain the list items<-->
Week2 - Exercise 2
Popular Websits related to HTML and the World Wide Web
HTML
Tim Berners Lee
Browser Stats 2018
- Browser Stats - W3Schools
- Wikipedia.org - The Browser Wars
- The True Story of the Internet Browser Wars (You Tube)
Future directions for the World Wide Web
Having summarized the origins of the Web, and its current state, we now look at some possible directions in which developments could take it in the coming years. One can separate these into three long term goals. The first involves the improvement of the infrastructure, to provide a more functional, robust, efficient and available service. The second is to enhance the web as a means of communication and interaction between people. The third is to allow the web, apart from being a space browseable by humans, to contain rich data in a form understandable by machines.
Infrastructure
When the web was designed, the fact that anyone could start a server, and it could run happily on the Internet without regard to registration with any central authority or with the number of other HTTP servers which others might be running was seen as a key property, which enabled it to "scale". Today, such scaling is not enough. The numbers of clients is so great that the need is for a server to be able to operate more or less independently of the number of clients.
Another cause for evolution is the fact that business is now relying on the Web to the extent that outages of servers or network are not considered acceptable. One would prefer an adaptive system which would configure itself so as to best use the resources available to the various communities to optimize the quality of service perceived. This is not a simple problem.
It includes the problems of:
- categorizing documents and users so as to be able to treat them in groups;
- anticipating high usage of groups of documents by groups of users;
- deciding on optimal placement of copies of data for rapid access;
- an algorithm for finding the cheapest or nearest copy, given a URL;
- Resolution of these problems must occur within a context in which different areas of the infrastructure are funded through different bodies with different priorities and policies.
These are some of the long term concerns about the infrastructure, the basic architecture of the web. In the shorter term, protocol designers are increasing the efficiency of HTTP communication, particularly for the case of a user whose performance limiting item is a telephone modem.
===== Assignment 3 =====
Week2 Exercise 3
TV LISTINGS
7.30pm
8.00pm
8.30pm
9.00pm
9.30pm
Monday
The Sunday Movie
News
Tuesday
TV Show
The Monday Movie
News
Talk Show
Wednesday
TV Show
Cops
Current Affairs
Wednesday
TV Show
Talk Show