Hello Paul,
I have already made a patch to the presence module to support a pure DB_ONLY mode (also
for presentities).
You can check it out on the master branch.
Regards,
Marius
________________________________
From: Paul Pankhurst <paul(a)crocodile-rcs.com>
To: Henning Westerholt <henning.westerholt(a)1und1.de>de>; sr-dev(a)lists.sip-router.org
Sent: Thursday, July 21, 2011 11:24 AM
Subject: Re: [sr-dev] DB_ONLY mode in presence module
Thanks for that Henning...seems to agree with some of the things I've seen in the
code.
I'm currently modifying all the presence related modules to support a pure DB_ONLY
mode.
I'm currently working on pua module, I'll check with Marius before I touch the
presence module
Paul
-----Original Message----- From: Henning Westerholt
Sent: Wednesday, July 20, 2011 12:14 PM
To: sr-dev(a)lists.sip-router.org
Cc: Paul Pankhurst
Subject: Re: [sr-dev] DB_ONLY mode in presence module
On Tuesday 19 July 2011, Paul Pankhurst wrote:
I’ve been looking through the presence module and have
some questions
regarding the DB_ONLY mode of operation.
Specifically the feature seems to rely on data not being written to hash
tables in certain areas of the code, as no checking is done to verify
which db_mode is being used.
However there are places where the hash table is populated irrelevant of
the db_mode, for example the init code calls pres_htable_restore.
Additionally update_presentity seems to also manipulate the hash tables
indiscriminately.
Am I missing something here, or is this a bug?
Hi Paul,
i think a similar question is discussed at the moment in the user list thread:
"xcap server - http load–balancer: xcap authentication problem"
Maybe you can have a look.
Best regards,
Henning
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev