Re: [reSIProcate] ServerRegistrationHandler --onExpired method is removed
Niraj wrote:
Hi,
In the DUM documentation I have seen that
class ServerRegistrationHandler have onExpired method
when client fail to refresh registration.
Unfortunately I am unable to see this method in the recently checked
out resiprocate.
My question is How can I now get client registration expiry at the
server side ?
The interface no longer provides this method. The original design
envisioned a base ServerRegistrationHandler that would actively track
expiration times. It turns out that such a one-size-fits-all solution
doesn't actually work. The tolerance a server has for detecting timeouts
varies widely depending on the applications it implements; at the same
time, the amount of processing that a server can dedicate to actively
monitoring expired registrations varies widely. Extremely high-volume
registrars may choose to perform registration expirations once a day,
during a non-busy hour. Presence servers that use registration state as
an input may need to find out within a few seconds of a registration
expiring. Those are the extreme ends of the spectrum, and there is a
pretty steady continuum of applications between those two.
As a consequence of this, it is now the responsibility of the
application to remove expired registrations as appropriate. Exactly how
you go about this depends on what the class that you derive from
RegistrationPersistenceManager does.
Two warnings in this area:
* The API for RegistrationPersistenceManager will be changing
radically in the near future.
* The InMemoryRegistrationDatabase is just a testing class that does
a pretty good job of demonstrating how
RegistrationPersistenceManagers need to work. It's not really
appropriate for any "real" work. You almost certainly want to
implement your own RegistrationPersistenceManager-derived class
that does some amount of replication and/or data persistence.
/a