I would go with the facade which calls the main cfc. Then flash and the webservices both can use the facade cfc.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Christian Cantrell Sent: Tuesday, October 21, 2003 11:08 AM To: cfc-dev Subject: [CFCDev] web service API I'm thinking of building an application that will have both a Flash and HTML interface. My initial thought was to encapsulate all my business logic in components which can be accessed by ColdFusion, then create a web service or Flash Remoting facade for the Flash interface. Another approach, however, would be to only create web services, and have both the Flash and ColdFusion interface use the components as web services. The advantages of an architecture like this are: - Simplicity. Just one external interface for both CF and Flash. - Distribution. I could potentially run the CF interface on a different server than the CF web services (though I must admit, I don't foresee a need to do something like this, but it still seems like an interesting option to have). The biggest disadvantage would probably be performance, although at this point, I don't have a good sense of how much additional overhead I would be dealing with. What do you guys think? Has anyone done something like this? Christian ---------------------------------------------------------- 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]
