Hi Doppelganger,

Yeah, I had a very specific requirement.  I was provided with an 
already-existing 4000-fuse reasonably standard FB non-XFB B2B application.  
The client wants to host multiple versions of this B2B app on one server, 
charging each of HIS clients a fair whack, and passing some of this on to me 
;-)

Of course, each end-client wants some customisations, mostly cosmetic, 
sometimes major.

Obviously, I could have ported the whole thing to an OO architecture, and 
all of that customisation stuff would have then been pretty trivial, but the 
porting is a VERY substantial task for an app of this size, and I'm doing it 
all on my little own.  Besides, I feel comfortable in CF, FB and even XFB, 
so I'd rather leave the app much as it is.

Answer:

* Port the FB into XFB.  Reasonably trivial, breaking some large fuseboxes 
up into smaller circuits;
* Make the location of every fuse a variable, set in myGlobals.  Use session 
scope, or some other smarts so that you don't have to set 4000 variables for 
every request (which would otherwise impose about 90ms overhead);
* Replace all calls to fuses within the fuseboxes indirect via the 
appropriate variable;
* Make this new "master" application the top-level XFB home app;

To make a clone:
* copy the index.cfm to a new sub-circuit;
* amend circuits.cfm as necessary
* copy and amend the odd fuse where customisation is required;
* use the circuit's myGlobals to override the default location of any 
customised fuses.

That's about it.  XFB makes it possible to have a hierarchy of 
customisations.  eg, the master app is "sub-classed" into German and English 
versions.  Then these are further "sub-classed" into "simple-interface" and 
"advanced-interface", etc.

Yeah, works fine.  XFB makes it easy, but it's also perfectly possible in 
non-XFB.

Oh m'God.  I can feel XXFB coming on.

See you later,
Leeb.


>From: "Hal Helms" <[EMAIL PROTECTED]>
>That has got to be the dumbest thing I've ever...
>
>Wait--what did you say? "XFB makes this very simple." Um, YES! I planned 
>all
>that out...uh, just like Lee says, inheriting the...the...thing that gets
>inherited using inheritance!
>
>Actually, that sounds pretty darned intriguing, Bjorkmeister. And it works
>well, eh?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to