CFCs and CLIENT Variables

[Cannikinn]

Okay, so our website uses CFCs for the customer's shopping cart. We
instantiate a copy of a Cart CFC object and store it in SESSION.Cart. We use
SESSION variables throughout the site so that as soon as the user closes their
browser, they're considered logged off. But we're re-thinking this scheme and
might want to keep them logged in forever (unless they manually logout). My
question is: Will it be possible to change my code so that the Cart object
is stored in CLIENT.Cart instead? Questions that came up in my mind: Will I
have to manually serialize/deserialize the entire object to and from WDDX each
time I need to access it? Would I be better off just using a CLIENT variable to
indentify the customer as being logged in, and then make sure that SESSION.Cart
always exists for them as long as they don't log themselves out of the site?
Thanks!

[Cannikinn]

Bump!

[byron1021]

CFC's can't be in the client scope. I believe if you do, you just get a string
that is a reference to the pointer for the original object. I think in MX 7,
clustered mx servers can serialize CFC's, but I think this is just for
Enterprise version's. You're probably best off using the client scenario to
keep the user logged in. and then have the cfc as a session var. Although
you'd need to persist the actual cart data somehow, which you'd probably wind
up doing in other client vars. So when the user comes back in a few days, you
can read the data that is supposed to be in their cart and create the
session.cart and populate it.