> Changing from session to client
>
> Are there any limitations on client vars, other than db size?
> Could structures and arrays be a problem?
Yes. If you want to store structures, arrays or queries in the Client scope,
you'll have to convert them to strings; you can easily do this with WDDX.
However, there will be a lot more overhead in doing this - the Client scope
is inherently more "expensive" to use. So, if you've got an application
which uses Session variables all over the place, you might have problems if
you simply switch to Client variables. You'd have to go through the
application and decide what you can do without when storing persistent data.
> Looking at the table, cdata, the client vars are all dumped
> into one field, can this be changed?
No. You're free to build your own alternative state management mechanism,
though; this is what we all used to do before Client and Session variables
anyway - you'd design the appropriate relational database structure, and
store your data in there, and simply retrieve it on each page request using
a regular SQL statement.
> and is there a way to automatically delete them when a user
> leaves your site with out logging out?
Not really, since you don't know when someone leaves your site. All you know
is that it's been a certain period of time since their last page request.
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
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
