On 11/6/05, Mark Leder <[EMAIL PROTECTED]> wrote: > Apparently, the onRequestEnd fires after the footer, so that's why the vars > weren't being set.
Yes the order of execution is: onApplicationStart() - if the app is not already initialized onSessionStart() - if the session is not already initialized onRequestStart() - before your page executes onRequest() - where your page executes onRequestEnd() - after your page executes onSessionEnd() - when the session times out (no active request) onApplicationEnd() - when the application times out (no active request) If you omit onRequest(), CFMX executes your requested page at that point. If you provide onRequest(), CFMX expects it to <cfinclude> your requested page. onRequestStart() is the closest equivalent to Application.cfm, onRequestEnd() is the closest equivalent to OnRequestEnd.cfm. > BTW: the previous problem with onSessionStart and Browserhawk was indeed a > browserhawk problem, which is being address in v9, due out Nov 10 (I got an > advance copy and it did solve the problem - runs much faster as well). Good to know! I wonder what they'd done wrong to cause it to fail in onSessionStart()? -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:223384 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