15 Jul
2011
15 Jul
'11
5:58 p.m.
On Friday 15 July 2011, laura testi wrote:
we have checked the presence extension for DB_MODE
only in the master
branch. But it's not complete DB_ONLY mode, it seems that it still uses
the cache for active_watchers in write through mode. Is there any reason
for it? That can still make problem for the scalability for the multiple
presence servers, because if an presence event (either SIP or XCAP) of an
active subscription in the cache of one presence server, goes to another
presence server, can still cause the problem even the DB is sync with the
cache.
Hello Marius,
maybe you can comment a bit on this?
Thanks and best regards,
Henning