That's not my advice. If it's session-based data, put it in the session. If it needs updating, update it. Why create additional load on your system by recreating everything upon each request?
-Dave On 6/25/06, Richard <[EMAIL PROTECTED]> wrote:
Thaks to everyone for their quick and detailed responses. A lot to take on board. However would I be oversimplifying things if say that the advice is not to instantiate objects in the session scope just to make data available for the session? On each page request, instantiate a new object and populate it from the DB or wherever? ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
