Magma, Seaside and Magrite integration

Facundo Vozzi facundov79 at gmail.com
Mon Nov 15 13:07:28 UTC 2010


Udo,

On Mon, Nov 15, 2010 at 7:11 AM, Udo Schneider <udo.schneider at homeaddress.de
> wrote:

> Facu,
>
> you might consider working with 1+n sessions. Use one (shared) session for
> all the general stuff and 1/session for session specific stuff.
>
> Another approach is to share a MagmaSession between Seaside sessions until
> a user logs in. Then you'll have a MagmaSession per logged-in user.
>
> e.g.
>
> MySystem>#magmaSession
>        | seasideMagmaSession |
>        seasideMagmaSession := WASession current magmaSession.
>        seasideMagmaSession notNil: [^seasideMagmaSession].
>        ^self sharedMagmaSession
>

Hi have a similar stuff, MySystem >> magmaSession is a session common to all
users, shared by all. But if a use an object in that session on a user
session a got an error. I need check it again.


>
> MyWASession>#magmaSession
>        ^magmaSession
>
> MyWASession>#loginUser: aUserName
>        magmaSession := self createMagmaSessionConnectAs: aUserName
>

Yes, I have this on MyWASession. I don't know because it's not working.


>
> Hope you get the idea.
>
> CU,
>
> Udo


Thank you again,
Facu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/magma/attachments/20101115/2db39c55/attachment.htm


More information about the Magma mailing list