On 10/29/07, Justin T <[EMAIL PROTECTED]> wrote: > > > Extension was something that I looked at as I use that extensively > already, but the two applications are not related at all. I didn't want the > onRequestStart, and onApplicationStart events firing in Canvas from my main > application. In addition, let's say there would be conflicting application > values.
If something hits the main Application.cfc, the Canvas onApplicationStart() etc. won't be run. Conversely, what if someone hits the Canvas app BEFORE the main application has been run? You may want that to bubble up to the main app so that it's onApplicationStart() runs, which means doing a super.onApplicationStart() if the main application isn't already set up. You could add a condition to this so it only happens if the main app isn't set up yet. If not, just don't call the superclass methods. I'm not sure what you mean by "conflicting application values", but these will probably need to be handled on a case by case basis. The bottom line is that to share the session scope between the two apps, they have to share the application name. It might be a good excuse to refactor things so that the application variables in the main app are segmented from the application variables in the child app(s). It's also a good demonstration of why one might not want to place lots of data directly into the base application scope but instead into structures within the application scope. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Get involved in the latest ColdFusion discussions, product development sharing, and articles on the Adobe Labs wiki. http://labs/adobe.com/wiki/index.php/ColdFusion_8 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:292249 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
