I didn't come here to split hairs over performance with you, just to provide
some code to the community.
Here's what my debug info says for a decent sized wddx packet...
15 ms 15 ms 1 CFC[ C:\Inetpub\wwwroot\framework\lib\cfcs\framework_rsession.cfc
| check() ] from C:\Inetpub\wwwroot\framework
I find 16ms hit hard to believe. You could have large caches of information,
structures, arrays of structures, and the hit to read and write that
information would go up significantly. The only difference between this method
and client variables is that you have converted it to wddx before you s
The functionality of this gives you more power over the scope than using client
variables. I've been using rsession since 2000, and working with the original
author I converted everything to more mx-friendly code. The hit to the db on
my servers only uses 16ms, which is not really and issue fo
I just looked at this code and while it solves a problem it creates another
one. You go from using session variables, to using the request variable (try
using cferror as a catch all on that scope, at least in cf 6) then you wddx it
all to a database. Why not just use client variables to begin wi
Hi all,
For those of you using rSession, I wanted to let you know that version
2.0is available, with better support for CFMX.
Here are some of the updates in the new version:
Uses CFC's instead of customtags
Session spy given a makeover
Cookies changed to use prefixes so that the component can
5 matches
Mail list logo