Re: Session bound components

Witek:


> what about components, requiring a session object? For example a 
> MailboxComponent for a web application. Every HTTP session needs an own 
> instance of MailboxComponent.

Yes, there is support for this, in one of several ways. Each user
session is assigned a "Context", which is essentially just like a Map -
you can get and put items to it. You can also access a unique session
id, and pass that on, or a UserEnvironment object (stored automatically
in the Context by the login process) to access login information.
Depends on the design you need. Ideally, you want to keep the amount of
data stored in context as small as possible, especially if you are in a
distributed environment (as the contexts must be synchronized accross
servers).

This Context info is used by Keel itself to determine authorization
(e.g. which user(s) can access which components)

I hope that answers your question, just let me know if you need more
details.

Mike
> 
> Is there a design pattern for session bound components in Keel?
> 
> Thank You, regards,
> Witek
> 
> _______________________________________________
> User mailing list
> [email protected]
> http://lists.keelframework.org/listinfo.cgi/user-keelframework.org