![]() It was the server’s responsibility to supply a resource corresponding to the requested URL initially, most of the resources were static HTML files or, at best, images. The HTTP protocol was created as a request/response protocol for client/server communication. There was also Gopher, which I am trying to forget. The response, an HTML file, was then rendered in an appropriate application, usually a browser. These documents were identified and located by a URL and retrieved by invoking the only HTTP method in existence: GET. In other words, a web of interconnected hypertext documents, connected via hyperlinks. The web, everyone’s favorite medium to find celebrity gossip and cat pictures, was designed as a linked information system. Keeping in mind the cliché above, and before diving into universal web applications, it would suit us well to go over their journey and discuss the challenges and triumphs experienced along the way. Enjoy! A Little Bit Of History “Those who don’t know history are destined to repeat it.” These applications will attempt to illustrate concepts, problems and decisions made along the way. In addition, we will go through a lot of code, progressively building an application, or rather a sequence of evolving applications.
0 Comments
Leave a Reply. |