Finally got my head round the session façade concept I think Found an example (Brian Koteks bookstore application www.briankotek.com) which illustrates this. My object is still in the session scope, but that is handled by another object which is responsible for creating it in that scope and getting setting it's properties.
As regards synchronising instance/backend data, I'm going to take Dave's advice at the top of this thread and commit the data as it is changed Thanks everyone -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Ross Sent: 25 June 2006 17:22 To: [email protected] Subject: Re: [CFCDev] Instances and persisted data 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? ---------------------------------------------------------- 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]
