Well, thanks for the clarification. Guess that's one advantage that was left
behind in FB3. I am sure it runs fine... but my perspective was incorrect.
(Translation: I WAS WRONG.) With that new information... Hal, I agree with
you that the advantage to going beyond an XML file would be imaginary. In
this scenario the current way is honestly the way I would do it also. (I
also store my multi-app configuration for SOS in an XML file also... but
have been looking at Cache for doing much more than just storing a
configuration set... it's quite a work of excellence.)

Thanks,

John Farrar

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Barney Boisvert
Sent: Friday, October 28, 2005 7:49 PM
To: [email protected]
Subject: Re: [CFCDev] CFSQLTool debate


To my knowledge none of the three frameworks allow multiple apps from
the same config file(s).  You can partition a single large app and use
certian pieces in different UIs, I suppose, but it's still all one big
app.  Mach-II will let you run multiple applications in a single CF
application, but each Mach-II app is still totally self-contained. 
Fusebox does not currently have that capability, and I'm not sure
about Model-Glue.

I believe Fusebox would be the closest in that you can use a single
circuit.xml file concurrently in multiple separate fuseboxes, but
again, that's just a "reusing a file" level thing (kind of like a
custom tag can be used in multiple apps), not really any sort of
multi-application support.

cheers,
barneyb




----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to