I'm not saying I like this technique--I don't--but if you're looking into
using CFC's as actions for forms, as Ian asked about, then Pollster is one
application where this is used and used effectively.
Hmm, I hadn't looked at the code of Pollster but I must say that I don't like that technique (for a variety of reasons, including Todd's comment about losing form variables) and I wouldn't recommend it.
With a hybrid HTML/Flash applciation such
as pollster you need to have both a CFM controller for regular HTML pages
and a CFC controller for Flash Remoting requests, but I would prefer that
these are just proxies to a centralized controller, which can be either cfm
or cfc--separate argument.
Totally agree. For example in Mach II, everything goes to index.cfm but it simply proxies requests (both GET and POST) to a request handler CFC within the framework. To mix Flash and CF UIs with Mach II, I would anticipate almost all of the back-end (Model) CFCs to be identical and only the controller layer to be different - a CFC for Flash and Mach II's index.cfm / controller / XML for CF/HTML. (I expect there is a neater Flash / Mach II integration but I haven't - yet - had a chance to dig in to how that might work yet).
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 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]
