With Fusebox, little will change. Previously, you did something like
this in index.cfm:
<cfapplication ... />
<cftry>
<cfif NOT structKeyExists(application, "appVarsLoaded")>
...
<cfset application.appVarsLoaded = true />
</cfif>
<cfinclude template="/fusebox4/fusebox4.runtime.cfmx.cfm" />
<cfcatch type="...">
</cfcatch>
</cftry>
Now you can move most of that (well, all of it, really) into
Application.cfc instead. Your Fusebox application itself will remain
completely untouched.
I suspect that Mach-II will not leverage Application.cfc for the
framework itself either, at least for a while. Application.cfc can
definitely help you do things in a better way, but it doesn't really
provide much that you can't accomplish in another way (the session
events are the main exception). Consequently, the benefits aren't
enough to make losing CF 6 compatibility reasonable. Again, you can
certainly leverage it for your own ends though, outside the framework.
cheers,
barneyb
On Mon, 7 Feb 2005 07:55:55 -0500, Calvin Ward <[EMAIL PROTECTED]> wrote:
> Any speculation or thoughts on how the new Application.cfc functionality
> might benefit the two larger frameworks?
>
--
Barney Boisvert
[EMAIL PROTECTED]
360.319.6145
http://www.barneyb.com/
Got Gmail? I have 50 invites.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:193545
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
