Thanks Matthew and Lance, this seems like exactly what I am after.
For our use cases, a temporary fix will be achieved with 0280 and
combining that with 0313 seems like a way towards a stable/permanent solution.
Stable in the sense that we want to handle all cases of syncing up resources in
active conversations
e.g. a resource going offline due to internet disconnectivity might loose a few
message with just 0280 in place.
0313 will help syncing back for various use cases we have in mind.
Finally, I would like to ask is there an existing implementation for 0280
inside ejabberd.
Even though 0280 looks quite straight forward, I will love to use an already
tested solution.
http://www.process-one.net/en/ejabberd/protocols/ indicates 0280 has already
been released in open source,
but where can I find it. ejabberd mainline (git) and ejabberd-modules (svn)
both doesn't seem to have it.
Thanks again.
Cheers,
--
Abhinav Singh,
Bangalore, India.
http://abhinavsingh.com
________________________________
From: Matthew Wild <[email protected]>
To: Abhinav Singh <[email protected]>; Jabber/XMPP software development
list <[email protected]>
Sent: Tuesday, September 25, 2012 4:30 PM
Subject: Re: [jdev] Keeping multiple connected resources in sync with chat
conversations
On 25 September 2012 08:30, Abhinav Singh <[email protected]> wrote:
> Hello Friends,
>
> I am exploring ideas on how to keep multiple connected resources of a user
> in sync with chat conversations.
> Has anyone worked on a similar use case?
I'm doing exactly this using XEP-0280 and XEP-0313 - they work well together.
Regards,
Matthew
_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected]
_______________________________________________
