Session management and scalability

A number of problems arise because HTTP is a stateless protocol. In the case of CW, it is necessary to keep track of the user’s Contenta Server connection and other information as the user navigates between pages. CW is using the HttpSession API provided with JSP to handle web server session management (as opposed to Contenta Server session management). This is a high-level interface built on top of cookies or URL-rewriting. On many servers, cookies are used if the browser supports them, but automatically revert to URL-rewriting when cookies are unsupported or explicitly disabled.