Yes! I am a fan of this trick myself, although I seldom need it. But even when I do, we are only talking small amounts of milliseconds of overhead. db-Client Variables Rules!!!
Can I say that louder ? C L I E N T S C O P E R U L E S !!!!@#$# Joey C. :-) --On Tuesday, June 04, 2002 8:37 AM -0500 Jeff Chastain <[EMAIL PROTECTED]> wrote: > > This one I have heard before and have a solution for (courtesy of Hal I > believe for today's environment of make sure credit is given). If you are > using structures, etc. all you have to do is use WDDX to turn it into a > single string and then store that string as a client var. Viola - you now > have complex client variables. > > > -----Original Message----- > From: Joseph Cochran [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 04, 2002 8:34 AM > To: [EMAIL PROTECTED] > Subject: Re: Client vs. session (was forcing user to login) > > > Greetings, (I'm mostly a big brother listener here) > The only con I see to client variables is no 'complex data' storage (ie. an > array of structures), but if your app requires that you need to persist > complex data, then you've got far greater problems with your app than > choosing between scopes. > > Once I went client scope (with a database baby!), > I never looked back! > Joey C. :-) > > > --On Monday, June 03, 2002 9:36 PM -0400 Jeff Peters <[EMAIL PROTECTED]> > wrote: > >> 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 >>> >>> >> >> > > > > _________________________________________ > Joseph C. Cochran II > Information Technology Services (ITS) > Systems Development & Implementation Team > Vanderbilt University > mailto:[EMAIL PROTECTED] > (615) 343-2244 > > > > _________________________________________ Joseph C. Cochran II Information Technology Services (ITS) Systems Development & Implementation Team Vanderbilt University mailto:[EMAIL PROTECTED] (615) 343-2244 ==^================================================================ 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 ==^================================================================
