15 Mar
2007
15 Mar
'07
2:06 p.m.
Hello,
In RFC 3903, which deals with Event State Publication, I have not found
how this cases should be dealt with.
Rajaram Tripathy wrote:
Hi,
Below is my scenario,
User1 is the watcher and User2 is the presentity
User1 sends SUBSCRIBE message to watch the presence inforamation of
User2.
User2 sends PUBLISH message, User1 gets notification.
After first PUBLISH User2 does not refreshes its publication.
Currently On expiry of presence information OpenSer sends NOTIFY
with status as "closed" in the first tuple. Is this behaviour is
correct ? Do we need to send NOTIFY with status as "closed" for each
"tuple" ? What is the correct behaviour ?
This action of sending a Notify with status closed was chosen to mark
that the presence information previosly notified is no longer valid.
Also when we send PUBLISH with Expire header as
"0", OpenSer sends
NOTIFY with the XML body as it is in the first PUBLISH. Is it right
behaviour ?
Thanks in advance.
Regards,
Rajaram
If you found some cases in which this solutions are not appropriate
please report.
Best regards,
Anca Vamanu
The information contained in this electronic message and any
attachments to this message are intended for the exclusive use of the
addressee(s) and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of
viruses. The company accepts no liability for any damage caused by any
virus transmitted by this email.
www.wipro.com
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users