|
|
STATE TRACKING |
|
|
Session information is cached on the server, not the browser. Every link available to the user contains a unique key that identifies both the user and the specific link to the system. The key is buried in the URL, bypassing the need for cookies and ensuring compatibility with even the oldest browsers.
Cookies are used to store state information for most interactive web site experiences. Since web servers do not keep track of content sent to different users, this information is usually stored on and accessed from the client browser using cookies. Cookies are the piece of information sent by a web server to a web browser that the browser software is expected to save and send back to the server whenever the browser makes additional requests from the server.
Depending on the type of cookie used, and the browser's settings, the browser may or may not accept the cookie, and may save the cookie for either a short or long period of time. Cookies are usually set to expire after a predetermined amount of time and are usually saved in memory until the browser software is closed down, at which time they may be saved to disk if their "time to expire" has not been reached.
With SiteHandler™ based web sites there is virtually no need to use cookies to keep track of session information. SiteHandler's™ method of tracking users allows information to be retrieved on a per-user basis. Although many firewall and gateway systems block cookies, the main reason why they are an unreliable means of keeping track of session information is simply that some people will choose not to accept them. With SiteHandler™, your web site will be available and fully functional to all users, and information you gather will be reliable and accurate.
|
|
|
