When Sessions Arent Enough

only for RuBoard - do not distribute or recompile

When Sessions Aren t Enough

Sessions in this chapter have consisted of a set of requests originating from a given client. When the session ID is stored in a cookie, a session is further limited implicitly to requests from a single browser, because any given cookie belongs to a specific browser. This approach works well for many applications, but sometimes you need additional capabilities. One limitation is that you can t access a session from multiple machines. For example, you can t suspend a session-based activity while at work, and then go home and resume it. When you need mobile session capability, other techniques can be used such as putting a front end on the session lookup process: Have the user log in using a name and password, and then use the name to associate the session with the user. These kinds of techniques lead us into consideration of security and authentication issues, which we ll take up in the next chapter.

only for RuBoard - do not distribute or recompile