Just finished reading Sean's article (on macromedia.com) re: RIA Design Patterns. I see the point of a session fa�ade and value objects and I've implemented similar things in RIAs in the past.
What I'm still a bit fuzzy on are the hooks into a CFC backend and the leveraging of CF's session management. Yes, I understand that the AMF header contains HTTP request info (or can). But what I'm fuzzy on where the session context is if you're only using CFCs for your backend integration. What I did in the past was pass a object back to Flash containing user profile info (after successful login) and have Flash maintain the user's state. If I were to instantiate a session scoped CFC instance would this continue to be available on subsequent requests from that client? If so, how? How is the application being defined, if there's no CFAPPLICATION tag? I had always thought that sessions where contained by applications. Jeff Battershall Application Development Consultant Dow Jones Indexes [EMAIL PROTECTED] (609) 520-5637 (p) (484) 477-9900 (c) ---------------------------------------------------------- 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]
