I assume you mean a CFC in the application scope that both CF and flash clients call methods (sendMessage(), getMessages(), etc.) on? You can do all the locking within the CFC, and encapsulate everything. Any time you manipulate instance data of the CFC, lock it, and you'll be good to go. Depending on your specific storage mechanism, you might not even need explicit locks, CF's or the DB's might be sufficient.
barneyb > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of John Farrar > Sent: Tuesday, November 04, 2003 3:37 PM > To: [EMAIL PROTECTED] > Subject: [CFCDev] Chat Object > > > I want to create a "persistant" chat object that can interact with CF > programs and Flash MX. The only issue that is of concern to me is that > access to the object would create conflicts. I am likely just paraniod > because I have used CF since before MX... and remember the need to "lock" > the application. Does anyone have special advice to offer... thanks in > advance. > > John Farrar > > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email > to [EMAIL PROTECTED] with the word '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] > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word '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]
