Are you SURE you really want to do that?! I would consider using some kind of client key and just persisting the objects in a database. I know there is the performance cost of the db call for each page request, but compared to serializing and persisting objects (possibly with relationships) using client variables, I’d at least consider it.
Can I ask why you’re getting rid of session variables? I’m guessing it’s to move to a multi-server load balanced solution that doesn’t have sticky sessions, but if it is another reason and you’re using a single server, I might even consider persisting the data in application scope (with the appropriate garbage cleaning routines you’d need to write) before I serialized everything to client vars.
Just my 2c.
Best Wishes,
Peter
On 9/8/06 2:14 PM, "Hayes, Kyle D" <[EMAIL PROTECTED]> wrote:
Hey All,
I just got news that in my new project I am not going to be able to store data in session variables anymore and have to resort to using client variables. My question to you all, since I cannot store my reactor record objects inside a client variable, is there a serialize function or similar available to me to serialize the data inside an object and then eventually convert to wddx etc? Thanks.
Kyle Hayes
Web Developer / Programmer
WebAID - Anaheim
Boeing Information Technology
714.762.2894
[EMAIL PROTECTED]
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[email protected]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[email protected]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
