> But when suggesting a move to a "plug-n-play" then *some* kinda
> standard has to be defined as absolute, even if it is minimal.
> And, to avoid a lot of the issues involved with versioning,
> there would have to be some version numbering system added
>
> ..skip..
>
Actually when I first saw the presentation on Fusebox Application Object
Model then I though "this is so similar how Spectra handles it". So my
suggestion is to look at Spectra's request-scope variables and use it as a
basis for Fusebox AOM.
See the Spectra Quick Reference for a list of Spectra request-scope
variables:
http://www.allaire.com/documents/spectra1docs/acrobatdocs/quickref.pdf
Erki
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
