Baz, It just kinda works. CF uses whatever uniquely identifies a client as the session identifier (actually, it is a combination of instance name, instance type, and identifier). You just refer to SESSION.var and CF worries about ensuring that you are getting the right session, timeout work just as they do with HTTP session variables.
--- Ben -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baz Sent: Thursday, January 19, 2006 8:28 PM To: [email protected] Subject: [CFCDev] CF Gateways and Persistent scopes Hi, How do Event Gateways in CF (SMS, XMPP, etc.) treat persistent scopes like session and application? I know that application.cfc runs like with any other file, but what exactly is a "session", if, for example, you are interfacing with GoogleTalk through the XMPP gateway? Does every request count as a new session? Does each GoogleTalk client get their own session ID? When does a session close? Cheers, Baz ---------------------------------------------------------- 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]
