The user send the data must read:

    The data could come from the Java Applet or from a custom HTTP client program but it is usually entered on a web page.

 Look up any other information about the request that is embedded in the HTTP request:

   The particulars about browser capabilities, cookies and the host name of the requesting client are contained in this row.

Results could be generated:

   That process may need converse to the executing cobra call or RMI to a database, computing the response directly or invoking a legacy application.

 HTTP response parameters are located: 

     What type of documents are getting back, seeting cookies and caching parameters.    

To client the document is send back:

    In any format like binary format, compressed format like gzip or in text format the document is send.

             There is an expansion of JSP from the Servlet technology. With the Servlets we can do anything in the JSP. On the other hand, with the code JSP agree to mix static HTML. Finally think about the page which is produced but in general it is easier to read the code.

         The static data is being printed to an output stream when the JSP page is individually changed to a normal Servlet in a nutshell. Still they both generate in the same output, in the Servlet real amount of code is written but there are many ways to decrease. We can read or write the JSP very easily. There is no difficulty in the usage of the JSP and Servlets because they have their individual roles and uses.