Hi Everyone. I'm new to this list, and new to CFCs, so bear with me if this is obvious. I'm struggling to decide how to handle the relationship between session instance data, and persisted data stored on the back end. I have a couple of related questions
1) If I have for example a session.user instance which has instance data that the user can modify (change email etc etc) should I commit this to the database at the same time in one transaction, or should I track whether the inszance data "is dirty" and manage the commit on the basis of an explicit save by the user, and maybe use the onSessionend event 2) If a user establishes two different browser session, we have effectively two different instances. This just complicates the above. Can I trap it (application variable?), or how should I handle this? I can always just reload instance data on each request, but that seems to defeat the purpose a bit I'm not sure whether these questions are just application related or whether they are CFC/component issues. Any pointers much appreciated Cheers Richard ---------------------------------------------------------- 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]
