I like this idea. I am wondering if every application has to initialise the framework?
Yes, each (sub-)application has its own instance of the framework CFCs. This is necessary since the AppManager is a manager for a single (sub-)application and knows about the filters, handlers, listeners, plugins and views for just that (sub-)application.
This seems like overhead for me.
The number of CFCs created and the amount of storage they take up is minimal.
It also allows each (sub-)application to be reloaded independently (even on a production system: edit index.cfm to add <cfset MACHII_CONFIG_MODE = 0/> then 'touch' mach-ii.xml and the application will reload on the next request - then change index.cfm back... note that you need the thread-safe version of mach-ii.cfm for this to work - available from my site now and will be in the next framework point release).
How are you calling events from another application? Using this url syntax (from app2): /root/app1/index.cfm?event=...?
You mean "How are you linking from one application to another?" - yes, just using URLs. But remember that the applications are essentially independent. As my blog entry says, if you want to invoke one application's CFCs (app1) from another application (app2), you need to access them from the listeners in app2 or, if they are listeners in app1, you need to declare them in app2's XML file.
What makes a (sub-)application is all about granularity. For example, on macromedia.com, the Online Store is an application, the product showcase is an application, trial downloads is an application - but the membership system is essentially a service, used by other applications (and communication of "logged-in-ness" is done via session scope).
Sean A Corfield -- http://www.corfield.org/blog/
Got Mach II? -- http://www.mach-ii.com/
----------------------------------------------------------
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]
