> allows you to provide an expiration. CFAPPLICATION automatically sets
> them with the equivalent of expiration="never", but sometimes it's
> nice to be able to make CFID and CFTOKEN expire when the browser
> closes, for example.
>
I wasn't disagreeing with what was suggested, just adding that there was a
"built-in" alternative. However, that being said, if you're using MX, why
not use J2EE sessions, which are browser-based and will automatically expire
when the browser closes? Regarding client variables, why use client
variables at all if I want them to expire when I close my browser? Doesn't
that defeat the purpose of using them to begin with (pre-MX clustered
environments where Session variables aren't available notwithstanding)?
Again, this isn't a disagreement with you or anybody else; I'm just curious
why the built-in features wouldn't be sufficient.
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
