[Standards] Chat continuation on different device
Hi, I frequently switch IM client running on different devices (mobile, laptop, ) and I would love to have a feature to continue last chat with some recent chat messages displayed on a new device. I have an idea how to implement it in the Tigase server and our mobile client (described below) and I was wondering if there is any XEP which could aid in this task from the protocol side. The idea is following: 1. User chats with a friend on one device 2. Server records and remembers somehow last chats (by thread id for example) 3. User switched devices and opens chat window with a friend in the second client 4. The client requests from the server last chat with this friend (we could add some parameters here, like last chat not older than 10 minutes for example) 5. If there is no chat history the server returns an empty list, otherwise the server returns a list of chat messages 6. The client displays messages received from the server and allows the user to continue conversation. I know of XEP-0136: Message Archiving which in theory could be used here as well. However, for once it is overkill for such a simple task and secondly the protocol requires a few packets exchange before the client can load last "collection" which increases traffic and delays. Artur -- Artur Hefczyc http://www.tigase.org/ http://artur.hefczyc.net/ smime.p7s Description: S/MIME cryptographic signature
Re: [Standards] PEP and PubSub
On 12/23/2011 07:50 AM, Florian Zeitz wrote: > Hello everyone, > Hello Florian, I am nice to meet you > The second thing I'm super uncomfortable with are the defaults mandated > by PEP. PEP mandates defaults for PubSub configuration options. Just > that PubSub never specifies some of those options. The only descriptions > of those options (e.g. deliver_notifications or access_model) are in > labels of form fields in the field standardization. > I personally don't deem those normative and would rather have some > normative text somewhere. Even if it's just a table with the same content. Offtopic slightly, but I already said that I see such problems too. For example, I said that it's impossible to say when pubsub service will publish item publisher attribute as said in http://xmpp.org/extensions/xep-0060.html#publisher-publish-success-publisher So it's impossible to say if pubsub server will be suitable if we need to know which author published which item. Such problems NEED to be solved too because, really, pubsub has great idea inside but it's impossible to build more high level protocols with such approach. > > Regards, > Florian "Florob" Zeitz > -- With best regards, Sergey Dobrov, XMPP Developer and JRuDevels.org founder.
