> I don't understand what your session components have to do with your DB > components. Why would you need DB specific session components?
I could be doing that wrong, of course. As it stands there is a lot of information gathered during a user's session. I collect a bunch of information about their User Agent, track all the pages of the application that they've visited (their "Clickstream"), and so forth. Once the session expires/times out this information is stored in a database for later use by application metrics. This is done via a "DP_Session.save()" method (I know that many people prefer "persist()" but they do the same thing). Right now this method injects DB-specific code into itself using CFINCLUDE and the DB type (as defined in an application-level component, DP_Application). Most of this was built specifically to address CF's inability to take "end-of-session" action, but there are other reasons. I'm now trying to determine (in the light of the CFINCLUDE-inside-a-method issue) how best to modify this code to ensure thread-safety. Jim Davis ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
