> I've got some
> pretty heavy-loaded client vars holding WDDX data, but its an
> intranet where
> there might be maybe 5-20 simultaneous users in a given app.
We got bitten by this big time on a project last year. We were wrapping
some variables in WDDX and stuffing them into out SQL Server DB as Client
Variables. However, there's apparently a 64K character limit on the total
string length of the client variable for any one client (ie. that pound-sign
delimited list that CF creates for the user's client variables cannot exceed
64 thousand characters in length). The word we got on this from the
engineers at Allaire was that it was a limit hardcoded into the function
that retrieves the client variables, over and above whatever limitations
your favorite flavor of db might have. Allaire suggested that we either
"roll our own" solution (I'm aware of several situations in which developers
have for one reason or another needed to re-invent the client variable wheel
and write their own routines for similar reasons) or rewrite our code using
session variables for storing our large wddx packets (the route we elected
to follow). The important point here is that they said it was NOT a
limitation, in this case, of the backend, nor of any long-text retrieval
settings in the CF Administrator.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
