> Additionally, if you convert complex data structures into WDDX,
> that will work well if your client vars are being stored in a
> datasource. However, if you're using cookies as you means of
> storing client variables, you'll need to be careful. Each cookie
> has a limit of 4kb in size. If you start dealing with complex
> nested data structures in WDDX, it's very easy to bump over 4kb
> in size with a WDDX packet.
Even if you're storing client variables in a database, you still want to
avoid storing complex data objects unnecessarily. If you don't, your
application will perform a lot slower using client variables than it would
with the same data objects in session variables.
I've seen this happen a couple of times; someone will have an application
which stores lots of data in the Session scope, they'll convert it to the
Client scope so that the application can be load-balanced, and it'll
essentially fail under load due to the database traffic.
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
