Kay, I copy session vars into a safe scope at the beginning of each request. Due to bugs in CF4.x's Duplicate(), I use WDDX to move between scopes. It's slower than Duplicate(), and unnecessary in CF5... but even with that in mind, my session2request.cfm contributes only a fraction to the overhead of a given page request.
IMX, most of it depends on what a few milliseconds mean to you. After all, there are some folks who have found the conceptually similar formurl2attributes.cfm too much of a performance hit. Personally, I look at it like this: if Macromedia ever gets around to making session variables safe for unlocked use, I'd rather go through old code removing "request." from calls to "request.session" than try to zap hundreds of unnecessary CFLOCKs. So I'm willing to surrender a few fractions of a second here and there. As for what constitutes "a lot" of session data... I dunno. I generally cache chunks of HTML (~50k), a few queries-within-structures, and so on in request.session without noticeable problems. -- Roger ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
