On 12/12/05, F Baube <[EMAIL PROTECTED]> wrote: > > Look in your WEB-INF/web.xml file; > > it's defined in the init-param "rep.path" > > I'm asking about this because I have previously discussed > making the file rep/users.xml (i.e. MemoryUsers) a writable, > updatable resource. > > A question for Geert is: > > If my authentication source is a _database_, and I call > RoleUsersManager addUser(..) or removeUser(..), is the > DB updated to reflect the change, as one would expect ?
Yes of course it is. > > Because the issue w.r.t. rep/users.xml is: If I write a > new class MutableMemoryUsers, and I call RoleUsersManager > addUser(..) or removeUser(..) on it, how do I tell Rife to > > 1) mirror the changes to rep/users.xml , AND AFAIK there is no way at the moment to write to users.xml. Note the Memory in MemoryUsers. It's stored in memory and is bootstrapped by the users.xml file. Nothing is stopping you from storing state in the XML file, but usage of a database is almost required in today's webapp world. I would strongly suggest just using an embedded database instead of trying to create some persistent memory cache. > > 2) update Rife's runtime authentication database > > In other words.. (a) how much of these is there already > support for, and (b) how much new code must be written, > and (c) where are the triggers to the Rife runtime engine. > > In any case it might be wiser to move to an in-DB authentication > source, if the addition and removal of users is already handled. > > > fred > > _______________________________________________ > Rife-users mailing list > [email protected] > http://www.uwyn.com/mailman/listinfo/rife-users > -- JR Boyens [EMAIL PROTECTED] _______________________________________________ Rife-users mailing list [email protected] http://www.uwyn.com/mailman/listinfo/rife-users
