Yeah - I agree. I like having a MutableRealm interface that the UI
knows about so that you could plug-in different realms with the same
UI. But probably the REST Service objects should talk directly to the
MutableRealm, not through the SM.
On Jul 18, 2008, at 3:00 PM, Dain Sundstrom wrote:
On Jul 18, 2008, at 11:49 AM, Jeremy Haile wrote:
Dain -
I'm really glad to hear that you're working on this. It would be
really awesome if you were able to open-source the GUI since I'm
sure that's something that would be useful to a lot of people for
getting their projects off the ground faster!
My idea would be something along the lines of having a MutableRealm
interface that had things like addRole( Object principal, String
roleName ) removeRole( Object principal, String roleName ).
createUser(....), etc. The UI that's built would then use the
MutableRealm interface to manage the users, roles, and permissions
within that realm. For REST support, I'd then think you would
want to have some Service objects that handle processing the REST
request and call the MutableRealm methods as needed. Is that
similar to the direction you're thinking of going?
Yes. I'm not building the GUI parts, but I will try to get the
person doing that on this list.
Side note: does it make sense to have a MutableRealmSecurityManager
interface that passes through calls to MutableRealms? Or does it
make more sense that the UI would interact directly with the Realms?
I'm not sure yet. I'm thinking that methods (addUser, addRole etc)
would only apply a single realm, I'm not sure it makes since to
expose them at the SM level, but who knows. After I get some basic
MutableRealm implementations, we can experiment with how to expose
the details.
Feel free to bounce ideas or questions off people on this list!
Will do.
-dain
