> Well, why not? Blanket statements like that sound fishy to me is all, > but if there's a good reason behind it... like maybe because lots of > sessions can be created by a crawler, for example. (But that could be > checked for an avoided.)
Probably because objects can hog up RAM. However this will vary depending on the size of your objects, number of concurrent users etc. If you are monitoring RAM usage with something like SeeFusion and have confidence that you have enough RAM in your machine to handle it, you'll probably be ok. If you are using user info on a lot of pages in your application, it makes sense to carry a user bean in the session scope, rather than re-instantiate or re-query on every page. -- Josh ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:274721 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
