Here, I'll give you a good reason for using client variable vs. session variables.
1.) Forget locking. You ain't got no locking with client-scoped vars. 2.) If the client-scoped vars are set up to be stored in a database instead of the Registry, and you'd be nuts to do otherwise, you then can query the database to get a look at the vars! Very easy to do. "SELECT * from CDATA WHERE..." You get the idea. 3.) Client-scoped vars survive a restart of the CFAS, or even a reboot of the server. > -----Original Message----- > From: Ney Andr� de Mello Zunino [SMTP:[EMAIL PROTECTED]] > Sent: Monday, June 03, 2002 4:51 PM > To: [EMAIL PROTECTED] > Subject: Re: forcing user to login > > 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 ==^================================================================
