AW: [riena-dev] Riena Session APIs

["Ziegler, Alexander" <Alexander.Ziegler@xxxxxxxxxxxx>]

Chris,

Thx. SimpleSessionHolderService explains everything. Now it is clear :-).

Something still is odd when I see this all. However maybe I figure out what this is.

sy
Alexander

-----Ursprüngliche Nachricht-----
Von: riena-dev-bounces@xxxxxxxxxxx [mailto:riena-dev-bounces@xxxxxxxxxxx] Im Auftrag von Christian Campo
Gesendet: Mittwoch, 13. Februar 2008 22:55
An: Riena Developers list
Betreff: Re: [riena-dev] Riena Session APIs

Hi Alex,

the point you are missing is that there is not a 1:1 relationship  
between ISessionHolderService and ISessionHolder. The
ISessionHolderService does not return THE ISessionHolder instance but  
YOUR ISessionHolder instance. While there is only
ONE ISessionHolder instance on the client (there is typically only one  
logged in user), there are many many ISessionHolder instances
on the server (one per thread). So the ISessionHolderService is  
relativly thin but not a simple GETTER. In distinguished between client
and server mode. The ISessionHolder is filled on the client by the  
SecurityCallHook (as you found out already). On the server that is
done by the SecurityServiceHook.

BTW the same happens in the ISubjectHolderService. It gets you the  
ISubjectHolder for relevant user. The ISubjectHolder then contains the
Subject.

hope that makes things more clear.

cheers
christian

Am 13.02.2008 um 17:43 schrieb Ziegler, Alexander:

> 2all,
>
> The Riena Session context provides some different interfaces.
>
> ISessionService - is the big player who provides session handling and
> becomes published as WS -> ok.
> ISessionProvider, ISessionStore - are the guys typically used within  
> the
> ISessionService -> ok. These interfaces looks also like
> integration-points for customer Provider and Stores.
>
> Now I'm a little confused about the ISessionHolderService and
> ISessionHolder... hmm...
> ISessionHolderService looks very thin. Its only provides a fetch- 
> method
> and its answers the ISessionHolder. The ISessionHolder defines
> getter/setter for Session object and jsession. Users have to inject  
> the
> ISessionHolderService, *only* to fetch the ISessionHolder instance  
> e.g.
> see SecurityCallHook.
> Maybe I'm wrong, but couldn't we vaporize this indirection?
>
> Some thoughts.. move the API of the ISessionHolder to
> ISessionHolderService. Move the fetch-methode and ISessionHolder to
> valhalla?
>
> Alexander
>
> _______________________________________________
> riena-dev mailing list
> riena-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/riena-dev

_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev