Considering the existing functionality of files like _serverSpecificRequestScope.cfm and farcryConstructor.cfm I wouldn't be opposed to simple CFM files that get included. It would be straightforward and fairly easy to implement.
Perhaps in the plugin's config folder you could have: onApplicationStart/End.cfm onSessionStart/End.cfm onRequestStart/End.cfm onError.cfm applicationConstructor.cfm (executed in the pseudo-constructor for things like this.mappings, etc) Alternatively, we could just have a single CFC (PluginApplication.cfc for example) that the core Application.cfc could look for, and if it exists, it could execute the methods during the proper portion of the request cycle. I am not sure how you would handle pseudo-constructor contributions (this.mappings, etc) in this case, but the single CFC seems a bit cleaner and is analogous to the Application.cfc itself. -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
