It is well known that the HTTP protocol to communicate with servers is actually a stateless protocol. This is good enough for point interactions, but what about an entire transaction? For example visualize the shopping cart scenario or airline reservation scenario. To complete one transaction, the user internally may have to connect and communicate with a server (or different servers) over a period of time. The question is how to achieve this over a stateless mechanism where each time is a different connection.

The problem is about how the server manages to connect pieces of information from each request that makes the transaction. This in turn translates into the problem of how the server (Servlet) identifies the multiple ...

Get Web Technology: Theory and Practice now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.