Hello,
In the DB_ONLY mode, every SUBSCRIBE request will trigger a database operation
immediately (either insert or update).
Also, the SUBSCRIPTION will always be matched from the database.
It behaves exactly as the name implies (write-through).
If it doesn't then that is a bug. Can you please tell me more about the
scenario you are using?
Is there any usecase in which you can see the subscription in memory but not in
the active_watchers table?
Regards,
Marius
________________________________
From: Henning Westerholt <henning.westerh...@1und1.de>
To: "Bucur, Marius Ovidiu" <marius.bu...@1and1.ro>
Cc: "sr-users@lists.sip-router.org" <sr-users@lists.sip-router.org>; laura
testi <lau.te...@gmail.com>
Sent: Friday, July 15, 2011 5:58 PM
Subject: Re: [SR-Users] xcap server - http load–balancer: xcap authentication
problem
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
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users