10 May
2008
10 May
'08
6:49 p.m.
Hi Pascal,
many thanks for the tip. Looks like a nice approach on a first glance.
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.
Wish you a nice weekend!
DanB
On Sat, May 10, 2008 at 10:47 AM, Pascal Maugeri <pascal.maugeri(a)gmail.com>
wrote:
Hi
I use the <timestamp/> element (section 4.1.7 of RFC 3863) of <tuple/> to
detect the most recent tuple and ignore the outdated ones.
Problem, the <timestamp/> is an optional element and your clients may not
insert it when publishing. Do you control the client source code that
publishes the presence information ? If no we should find a way in openser
presence module to add this timestamp element for you. I add a quick look at
PRESENCE and PRESENCE_XML but I haven't find anything yet.
Regards,
Pascal
On Fri, May 9, 2008 at 12:02 PM, Dan-Cristian Bogos <
danb.lists(a)googlemail.com> wrote:
Guys,
while dealing with presence/presence_xml modules, I came into one
situation when one user crashes simultaneously and each time displaying
different presence info (online, away, offline). Have noticed that the
presence server is smart enough to inform all the other watchers about three
different status information for the same user.
My question is, how can the watcher know the most recent status
information. Have looked on both order of info in the tuple as well as on
ids but did not find any logic. Can u please guide me about possibilities I
have?
Thank you in advance,
DanB
PS: FYI, I am pasting such a tuple example.
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="t9062">
<status xmlns="urn:ietf:params:xml:ns:pidf">
<basic>closed</basic>
</status>
</tuple>
<dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
id="p8838"><rpid:activities/></dm:person>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="t5358">
<status><basic>open</basic></status><contact>sip:user@domain.com<sip%3Auser@domain.com>
</contact><note>Online</note>
</tuple>
<dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
id="p4226"><rpid:activities><rpid:away/></rpid:activities></dm:person>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="t7139">
<status><basic>open</basic></status><contact>sip:user@domain.com<sip%3Auser@domain.com>
</contact><note>Away</note>
</tuple>
<dm:person xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
id="p4606"><rpid:activities/></dm:person>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="t5632">
<status><basic>open</basic></status><contact>sip:user@domain.com<sip%3Auser@domain.com>
</contact><note>Online</note>
</tuple></presence>
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users