Hey All: Been playing around with Model-Glue 3, perusing the docs, learning all the new cool tricks.
Looking at Application.cfc integration, where MG will automatically broadcast messages for onApplicationStart, onSessionStart, and onSessionEnd. Curious as to what the advantage of this is? If the framework is supposed to be "black-boxed" from Application and Session (which may be the subject of another discussion entirely), I'm not able to think of a use-case where I'd want to do anything specific inside of the framework on these events. onApplicationStart fires once, when the application fires up. What would I potentially want to do inside of Model-Glue specifically on that event? Same with onSessionStart and onSessionEnd? Wouldn't anything that I want to do on these events happen in the corresponding method in Application.cfc? What could exist inside of MG that I'd want to handle only inside of MG, as opposed to using Application.cfc itself? Any thoughts? Anybody making use of this feature? Thanks, Charlie -- I have failed as much as I have succeeded. But I love my life. I love my wife. And I wish you my kind of success. --~--~---------~--~----~------------~-------~--~----~ Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en -~----------~----~----~----~------~----~------~--~---
