> IMO. I will never use session variables again for a shopping
> cart. WDDX/Client Variables is the way.
Interesting. I was working on a very large, complex application a couple of
months ago where client variables & WDDX got us in big trouble; seems like
there's a limit on the total length allowed for all client variables
associated with a single client. We were stuffing (sometimes rather large)
WDDX structures into client variables, ran into a problem, and were told by
Allaire that the total length allowable for client variable storage is 64
thousand characters (premiere support, this was from the Sr. Engineer
assigned to our account). This is apparently not related to the flavor of
db that is backending the system; I'm not sure, but I think it may possibly
be related to the string parsing functions that handle getting your client
variables in and out of that pound sign delimited list in CDATA.DATA. They
suggested we write our own routines for essentially duplicating what client
variables do, or switch to session variables and accept a loss of state in
our cluster when there was a failover.
I'd be most interested in hearing if anybody else has run into this issue;
I've never heard of this happening to anyone else, and I know there's got to
be a few others out there that are putting WDDX into client storage.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
