<snip>
>
> I think there are (at least?) 3 ways of managing state information:
> * URL rewriting (small amount of state information is attached to
> the URL -
> the advantage of this is that all browsers support it)
> * Cookies (quite popular method - but requires cooperation from user -
> ie. enabling cookie support in the browser)
> * embedding a session identifier in a hidden html form field, and passing
> the information back to the application server.
> The application server matches up the session identifier and tracks
> the state of the user's session.
And the beauty of using a decent app server, is that you as a programmer
don't have to worry which method you follow. You can treat the session state
as an object and let the app server manage it thro' one of the above methods
via administration.
-- Aravind
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
