| < Previous by Date | Date Index | Next by Date > |
| Thread Index | Next in Thread > |
[reSIProcate] RegistrationPersistenceManager
- From: "Matthias Moetje" <moetje@xxxxxxxxxxxx>
- Date: Tue, 16 Jan 2007 00:43:29 +0100
|
Hi, I am currently trying to figure out what the lockRecord and
unlockRecord functions in the RegistrationPersistenceManager are required for. Is the assumption correct that this is only required when
using in-memory registration? I am currently creating my own RegistrationPersistenceManager
(for storing into an SQL database) and I don’t understand the necessity
of lock and unlock. What is this required for? Also the removeAor function seems to be specific for
in-memory registration, in a database you would not want to delete a user record
but rather only erase its contact list..? And a final question: Why does repro persist the ACL to a
database but not the registrations, wouldn’t it be more logical to do it
the other way round (when the ACL store is lost, clients would only
automatically re-authenticate, but the situation is worse when registrations
are lost)? Best regards, Matthias Moetje
| |||||||||
- Prev by Date: [reSIProcate] build challenge (407) after requiresChallenge() in DUM
- Next by Date: [reSIProcate] RegistrationPersistenceManager
- Previous by thread: [reSIProcate] build challenge (407) after requiresChallenge() in DUM
- Next by thread: [reSIProcate] RegistrationPersistenceManager
- Index(es):