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 for me.
> 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 with? I try to stay away from client variables or > reading and writing excessively to a database because my database > server is the bottleneck in any of my applications. > > I think this app would be much cooler if you could actually duplicate > your session and application variables on another server so that when > your server fails over to the other one, the memory variables are > already there. > > > Bob ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:238147 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
