John Farrar wrote: > Has anyone looked at doing this with MX and CFC's?
One of the first things I did with MX was set up a "CFC-FB". Each "circuit" was an inherited component rather than a nested directory of files, and calling multiple fuseactions within a single request was as simple as invoking any other component. I also threw in some other ideas I was playing with... like a "viewer.cfc" that would allow an app to produce HTML for a browser with a fuseaction like "html.dothis" and XML for a web service with "wddx.dothis". I haven't played with it much, though, for two reasons: (1) At least in the pre-release, CFMX's error reporting is a bit obscure when it comes to CFCs. Figuring out exactly which component blew a fuse can be annoying. (2) I'm not sold on the need for it. Yeah, it allows you to do some fairly cool things, but in the end, it may be easier (and more productive) to simply use CFCs as fuses in the context of a traditional FB app. -- Roger ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
