Thursday, 20 June 2013



  • Most web application run on HTTP.
  • HTTP is a stateless series of client/server message exchange protocol.
  • Normally client is web browser, server is web server/application server.
  • The client initiates communication by requesting a specific resource.
  • The resource may be a HTML file, or dynamically generated output.
  • HTTP originally designed for requesting and serving static HTML documents.
  • HTTP is an application layer protocol 

  • One of cons of HTTP is, it is stateless protocol. It doesn't maintain the state between multiple request from same client. Server don't know whether the next request is come from same user/client.
  • The server has the client's address, but it will only be used to return current requested document.
  • If we try to build a web application with complicated use case, the above won't help.
  • Simple example is a secure web application must authenticate it users. To do this, the request in which client send username and password must associate with all other request coming from that client during the user session.
  • HTTP is also a text based. Mating text based technology to a strongly type based such as Java creates significant amount of data-binding work.

No comments:

Post a Comment