> Are you saying it is better you session (or) client
> variables, but not both. I just am trying to learn what
> the meaning of that was since i am fairly new.
Generally, you don't need to use both at the same time. They're both used
for essentially the same thing - managing user information across multiple
requests.
Session variables:
- stored in memory
- typically used to store user-specific information across multiple requests
during a single site visit
- allow direct storage of complex data objects (queries, arrays, structures)
- don't work in a fully clustered and load-balanced environment
Client variables:
- stored somewhere else (database, cookies, registry)
- used to store user-specific information across multiple site visits
- can only store string information (WDDX can be used to convert complex
data objects to strings)
- can be used across a cluster
While you might want to store some information across site visits, and not
store other information, you'd still typically just use one or the other.
For example, if clustering isn't going to be needed for an application,
you'd probably use session variables, and at the beginning of any site
visit, you'd query a database to populate those session variables with the
appropriate data for that user.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
