Sean, do you still keep your site's CFCs "outside" the web root?  Are only the 
remoting CFCs located in the /remote directory?

Thanks

-----Original Message-----
From: Sean A Corfield [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 29, 2004 2:07 PM
To: [EMAIL PROTECTED]
Subject: Re: [CFCDev] CFC Session Fa�ade for Flash RIAs

On Apr 29, 2004, at 11:32 AM, Barney Boisvert wrote:
> Personally, I wouldn't use Application.cfm for flash remoting and/or 
> web services.  Too much mixing of paradigms for my tastes.

What I would suggest is considering this sort of structure:

        /webroot
                Application.cfm
                /remote
                        Application.cfm

And then keep all of your remote CFCs in /remote - that Application.cfm would do 
nothing beyond setting the application name and enabling session scope. If you're 
using cflogin and setCredentials() (I think that's the Flash gateway method) then 
you'll need <cflogin> in Application.cfm to maintain roles and logged in session data.

Of course, I'd also recommend keeping your Application.cfm files as simple as possible 
anyway!

Sean A Corfield -- http://www.corfield.org/blog/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood

----------------------------------------------------------
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]
----------------------------------------------------------
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]

Reply via email to