On Jul 21, 4:37 am, Dan Wilson <[email protected]> wrote: > I tend to abstract retrieving the entity rather than the scope. > > For example, I have a currentUserLoader that accesses the session directly > and eventually returns a populated user object, or a blank one. >
The major issue I've come across with this is integration into other applications. For instance CanvasWiki uses a session facade so when we wanted to integrate it with our other applications with unified login our layout engine and other things it was a trivial matter to set the APP_KEY for MG and then swap out the SessionFacade in Canvas to store in session ["canvasWiki"] instead of directly in the top level session scope. With your approach (which is admittedly somewhat simpler), you couldn't just swap out the Facade, you'd need to edit each service component that touched a shared scope. When you access the session and application scopes directly it becomes much messier to integrate many applications with an APP_KEY since they have a tendency to step on each other. --~--~---------~--~----~------------~-------~--~----~ 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 For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
