Hi Anca
Thank you. I will test your bug fixing tomorrow morning and will let
you know the results ASAP.
Could you please point out where you found the last NOTIFY should have
a body, please ?
Do you have any data to share with me regarding the stability of
presence module (memory leak, thread leak, CPU, etc.). Is it stable
over time ?
Regards,
Pascal
On Nov 13, 2007 3:56 PM, Anca Vamanu <anca(a)voice-system.ro> wrote:
Hello,
When dealing with the problem you reported I found that it might be that
a body is required in Notifies following an unsubscribe message. I have
made the changes to include this and also fixed the problem with the bad
status. Please test and provide feedback.
Thanks and regards,
Anca Vamanu
Pascal Maugeri wrote:
Hi
I'm doing stability testing against presence module and after
"several" requests an un-subscribe request (SUBSCRIBE with Expires=0)
triggers a NOTIFY with a payload and the following Subscription-State
header value:
Subscription-State: active;expires=0
In my humble opinion this is incorrect as the RFC 3265 section says in
section 3.3.6:
Note that the NOTIFY messages triggered by SUBSCRIBE messages with
"Expires" headers of 0 will contain a "Subscription-State" value
of
"terminated", and a "reason" parameter of "timeout".
Ref.:
http://tools.ietf.org/html/rfc3265#section-3.3.6
Best regards,
Pascal
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users