Hello Anca,<br><br>thank you for the clearance. All bright now.<br><br>It looks like there was a false alarm from the developer I work with since the order of the tuple was first thing we checked, but since the xml was processed as DOM he did not receive the info in order. <br>
Now he confirmed me that the order is properly received in the UA.<br><br>Wish you a lovely afternoon.<br><br>DanB<br><br><div class="gmail_quote">On Mon, May 12, 2008 at 12:40 PM, Anca Vamanu <<a href="mailto:anca@voice-system.ro">anca@voice-system.ro</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Dan,<br>
<br>
In fact, the presence modules orders the tuples in the Notify body after the time the Publish was received. So, you will always have the most recent information first.<br>
<br>
Regards,<br>
Anca<br>
<br>
Dan-Cristian Bogos wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="Ih2E3d">
Hi Pascal,<br>
<br>
many thanks for the tip. Looks like a nice approach on a first glance.<br>
<br>
I use sip-communicator and am in contact with the developers. Will try the approach for the client then, but the idea with the timestamp on the server side could help much more people hitting the same issues and not able to touch their clients.<br>
<br>
Wish you a nice weekend!<br>
<br>
DanB<br>
<br></div><div class="Ih2E3d">
On Sat, May 10, 2008 at 10:47 AM, Pascal Maugeri <<a href="mailto:pascal.maugeri@gmail.com" target="_blank">pascal.maugeri@gmail.com</a> <mailto:<a href="mailto:pascal.maugeri@gmail.com" target="_blank">pascal.maugeri@gmail.com</a>>> wrote:<br>
<br>
Hi<br>
<br>
I use the <timestamp/> element (section 4.1.7 of RFC 3863) of<br>
<tuple/> to detect the most recent tuple and ignore the outdated ones.<br>
<br>
Problem, the <timestamp/> is an optional element and your clients<br>
may not insert it when publishing. Do you control the client<br>
source code that publishes the presence information ? If no we<br>
should find a way in openser presence module to add this timestamp<br>
element for you. I add a quick look at PRESENCE and PRESENCE_XML<br>
but I haven't find anything yet.<br>
<br>
Regards,<br>
Pascal<br>
<br>
On Fri, May 9, 2008 at 12:02 PM, Dan-Cristian Bogos<br></div><div><div></div><div class="Wj3C7c">
<<a href="mailto:danb.lists@googlemail.com" target="_blank">danb.lists@googlemail.com</a> <mailto:<a href="mailto:danb.lists@googlemail.com" target="_blank">danb.lists@googlemail.com</a>>> wrote:<br>
<br>
Guys,<br>
<br>
while dealing with presence/presence_xml modules, I came into<br>
one situation when one user crashes simultaneously and each<br>
time displaying different presence info (online, away,<br>
offline). Have noticed that the presence server is smart<br>
enough to inform all the other watchers about three different<br>
status information for the same user.<br>
<br>
My question is, how can the watcher know the most recent<br>
status information. Have looked on both order of info in the<br>
tuple as well as on ids but did not find any logic. Can u<br>
please guide me about possibilities I have?<br>
<br>
Thank you in advance,<br>
DanB<br>
<br>
PS: FYI, I am pasting such a tuple example.<br>
<br>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="t9062"><br>
<status xmlns="urn:ietf:params:xml:ns:pidf"><br>
<basic>closed</basic><br>
</status><br>
</tuple><br>
<dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"<br>
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"<br>
id="p8838"><rpid:activities/></dm:person><br>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="t5358"><br>
<status><basic>open</basic></status><contact><a href="mailto:sip%3Auser@domain.com" target="_blank">sip:user@domain.com</a><br></div></div>
<mailto:<a href="mailto:sip%253Auser@domain.com" target="_blank">sip%3Auser@domain.com</a>></contact><note>Online</note><div class="Ih2E3d"><br>
</tuple><br>
<dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"<br>
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"<br>
id="p4226"><rpid:activities><rpid:away/></rpid:activities></dm:person><br>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="t7139"><br>
<status><basic>open</basic></status><contact><a href="mailto:sip%3Auser@domain.com" target="_blank">sip:user@domain.com</a><br></div>
<mailto:<a href="mailto:sip%253Auser@domain.com" target="_blank">sip%3Auser@domain.com</a>></contact><note>Away</note><div class="Ih2E3d"><br>
</tuple><br>
<dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"<br>
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"<br>
id="p4606"><rpid:activities/></dm:person><br>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="t5632"><br>
<status><basic>open</basic></status><contact><a href="mailto:sip%3Auser@domain.com" target="_blank">sip:user@domain.com</a><br></div>
<mailto:<a href="mailto:sip%253Auser@domain.com" target="_blank">sip%3Auser@domain.com</a>></contact><note>Online</note><div class="Ih2E3d"><br>
</tuple></presence><br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br></div>
<a href="mailto:Users@lists.openser.org" target="_blank">Users@lists.openser.org</a> <mailto:<a href="mailto:Users@lists.openser.org" target="_blank">Users@lists.openser.org</a>><div class="Ih2E3d"><br>
<a href="http://lists.openser.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.openser.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
<br></div>
------------------------------------------------------------------------<div class="Ih2E3d"><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.openser.org" target="_blank">Users@lists.openser.org</a><br>
<a href="http://lists.openser.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.openser.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</div></blockquote>
<br>
</blockquote></div><br>