I think of client variables as session variables with added options. The options being:
- Protection from clustering problems. - Choice of storage methods - Cookies - The database of your choosing - Registry (not recommended, but available nonetheless) I've seen no metrics to compare performance of session variables vs. the various types of client variables, but I'd imagine that session vars would enjoy some advantage, in that they are based in server memory, as opposed to disk-based storage like client variables (either on the server in the case of the database or registry options, or on the client in the form of cookies). That said, I've long since given up the use of session variables in favor of client variables (in a database), simply to be able to forgo future problems if an app is dropped into a clustered environment. - Jeff On 4 Jun 2002 at 9:50, Ney Andr� de Mello Zunino wrote: > Troy Murray wrote: > > > I'm curious, other then having clustered environments, was there > > anything else that lead you to use CLIENT vs. SESSION variables? > > I share the same curiosity. What are the pros and cons of client and > session variables? Would anyone be able to explain in easy terms? > > Thank you, > > -- > Ney Andr� de Mello Zunino > Media and Technology Laboratory > Campus Computing Centre > United Nations University > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
