[Seaside] Re: authentication for seaside

Andy Burnett andy.burnett at knowinnovation.com
Wed Dec 29 16:35:22 UTC 2010

Ramon said...
I was thinking more in terms of a user being a domain object and how
you'd deal with adding/finding/removing users in a generic
authentication plugin in a persistence neutral manner that wouldn't need
rewritten once a final persistence mechanism was chosen.  It would not
be done the same way in Glorp as in Gemstone for example.  Perhaps it'd
be more of a mini-framework where you'd have to subclass a few things
and fill in a few blanks before things worked.


OK, thanks.  I could deal with needing to subclass a few classes, so long as
the basic framework dealt securely with the basic mechanics of the user
accounts, and creating and managing the session cookies etc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20101229/b085c43c/attachment.htm

More information about the seaside mailing list