This subject has been seen and answered by sean Corfield in the mach-ii
forum.
This is the thread:
http://www.fusebox.org/forums/messageview.cfm?catid=26&threadid=2482&highlig
ht_key=y&keyword1=app
The answer is that you can have multiple mach-ii application. You just need
to have the same name in the cfapplication tag to share ressource between.
I didn't test it
Denis Lamotte
On 21/01/04 11:20, "Nando" <[EMAIL PROTECTED]> wrote:
> I just noticed this topic being discussed both in the new Mach-II
> Request-Event-Exception Handling article that Ben just published on the
> mach-ii site
> and the macromedia mach ii dev guide. From what i've just read in the new
> Request-Event-Exception guide - "Each Mach-II application has one instance of
> a
> RequestHandler that is created when the application is initialized."
>
> and in the macromedia mach ii dev guide ... the live docs one online -
>
> "... you can set your own values for MACHII_CONFIG_MODE, MACHII_CONFIG_PATH
> and, if
> needed, MACHII_APP_KEY. By default, the mach-ii.cfm core file uses the
> directory in
> which the request originated ({appname} in our example) as a key into
> application
> scope to store that application's instance of the framework objects. "
>
> It seems that each application, as defined by a unique MACHII_APP_KEY,
> initializes
> some instances of objects, like the RequestHandler mentioned above, unique to
> the
> application - i guess depending on whether those objects need to maintain
> instance
> data unique to the app ... The new Request-Event-Exception Handling article,
> although
> simple and concise, is a good read.
>
> Nando
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Harry Klein
> Sent: Wednesday, January 21, 2004 10:05 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [CFCDev] Multiple MachII Apps
>
>
> Excerpt from an older Mach II forum entry by Sean:
>
> "... we have a single cfapplication name across the entire site and then
> each Mach II application uses a distinct MACHII_APP_KEY. It works really
> well!
>
> If you build a Mach II application in /app1 and another one in /app2,
> all you need to do to make them share space is to have
> /app1/Application.cfm and /app2/Application.cfm both be very simple - no
> cfapplication tag, just cfinclude /Application.cfm which defines a
> single application name for both app1 and app2
>
> The CFCs can reside anywhere so one application's XML file can access
> another application's CFCs. The likelihood of just being able to
> announce events in another application and expect them to work from your
> application is slim to zero. However, if you wanted to use the Contact
> Manager's listener CFC to create contacts when you processed a sale
> event, you could simply declare the CFC as a listener in your
> application (a couple of lines of XML) and then notify it to create the
> contact (and likely map the events it announces). That last point is key
> - the events announced by listeners should be application-neutral,
> precisely to allow this level of reuse."
>
>
> I like this idea. I am wondering if every application has to initialise
> the framework?
> This seems like overhead for me. Maybe it makes sense for completely
> independent apps, but if we are using this technique to split one big
> application into more parts?
> How are you calling events from another application? Using this url
> syntax (from app2): /root/app1/index.cfm?event=...?
>
> --
>
> Harry Klein | Konzeption und Entwicklung
> CONTENS Software GmbH
>
> Oettingenstr. 25 | 80538 M�nchen
> Fon: +49 (0)89 5199 69-0 | Fax: +49 (0)89 5199 69-78
> mailto:[EMAIL PROTECTED] | http://www.contens.de
>
> ******************************************
> Besuchen Sie CONTENS auf der
> iEX Internet Expo 2004 in Z�rich
>
> 04. - 06. Februar 2004
> Halle 5, Stand 5.163
>
> Mehr Infos finden Sie hier:
> www.contens.de/iex <http://www.contens.de/iex>
> ******************************************
>
> ----------------------------------------------------------
> 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]
>
----------------------------------------------------------
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]
