I agree totally and I understand that. My issue is with storing
(adding) values to my struct before serializing it and *then* storing it
in Client scope.
My real question is why can I *add* to the struct while using sessions
and wrapping <cflock> around it ... but I can't do with local scope (no
session or client) defined.
Best Regards
________________________________
From: Paul Vernon [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 21, 2004 8:42 AM
To: CF-Talk
Subject: RE: Session to Client workaround
If you want to store structs in the Client scope, you have to serialise
them.
The Client scope cannot cope with complex variables as it has to be able
to
store the entire client variable scope in a single cell in a DB. Even if
you
choose not to use a DB to store the Client scope, the same rule applies.
Paul
________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
