One more thought on this. You can think of the facade object as the one and only "doorway" to the session scope for your application. If you find that later you need to store another bit of information in the session scope, do that though the facade object as well.
Dan On Aug 4, 2010, at 11:46 PM, Irv Wilson <[email protected]> wrote: > Thank you! > > So setting session.userid at login and then having something like > > function - getuser() > lock > set userid = session.userid > /lock > return userid > > in a scopefacade bean seems ok? > > > -- > 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 -- 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
