Hello,
a short reminder about freezing the development for next major release v3.3.0. It is planned for April 23, less than two weeks away. If you have new features to add for v3.3.0, commit them or send the patches before the date.
Cheers, Daniel
Hi,
One of the developments I am currently working on is to add notifier processes to presence. I have already done this for RLS. This is needed not just for performance, but because there are race conditions (I see them under load) where you get multiple NOTIFY requests outstanding on the same dialog and, when in DB only mode, they often have the same CSeq (despite being different requests).
Unfortunately, I don't believe I will get this finished by the end of Monday (April 23). I still expect to complete this development next week.
As the CSeq issue is quite clearly a problem I would like to get this development into Kamailio 3.3. Will it be OK for me to put this development into master next week after the freeze?
Thanks,
Peter
On Wed, 2012-04-11 at 11:34 +0200, Daniel-Constantin Mierla wrote:
Hello,
a short reminder about freezing the development for next major release v3.3.0. It is planned for April 23, less than two weeks away. If you have new features to add for v3.3.0, commit them or send the patches before the date.
Cheers, Daniel
Hello,
On 4/19/12 7:33 PM, Peter Dunkley wrote:
Hi,
One of the developments I am currently working on is to add notifier processes to presence. I have already done this for RLS. This is needed not just for performance, but because there are race conditions (I see them under load) where you get multiple NOTIFY requests outstanding on the same dialog and, when in DB only mode, they often have the same CSeq (despite being different requests).
Unfortunately, I don't believe I will get this finished by the end of Monday (April 23). I still expect to complete this development next week.
As the CSeq issue is quite clearly a problem I would like to get this development into Kamailio 3.3. Will it be OK for me to put this development into master next week after the freeze?
as long as it fixes an existing problem, then it has to be done anyhow. So for me it's ok, others can comment here if they have different opinions.
Cheers, Daniel
Daniel-Constantin Mierla writes:
So for me it's ok, others can comment here if they have different opinions.
ok with me too provided that there no changes to db schemas. if there is, schema changes should be done before the freeze deadline.
-- juha
OK. I am going to add one new column to the active_watchers table for the notifier.
I will commit that addition today, but the new column won't be used until the notifier code is completed and checked in.
Peter
On Fri, 2012-04-20 at 13:02 +0300, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
So for me it's ok, others can comment here if they have different opinions.
ok with me too provided that there no changes to db schemas. if there is, schema changes should be done before the freeze deadline.
-- juha
-
Daniel-Constantin Mierla -
Juha Heinanen -
Peter Dunkley