Support 7.9 Converting a One-to-One Chat Into a Multi-User Conference (#34)

Support 7.9 Converting a One-to-One Chat Into a Multi-User Conference (#34)

Activities

	wojciech.kapcia@tigase.net opened 1 decade ago Add support for 7.9 Converting a One-to-One Chat Into a Multi-User Conference
	Artur Hefczyc commented 1 decade ago I think this question is mainly for Bartek as he know protocol the best, probably Andrzej also knows the MUC much better than I do. I am not sure how deep Wojciech has dug into it. I am probably the least competent to thrown any ideas. So anybody has any suggestions how we could do this, add your comments here. This actually might be a very nice feature for the mobile messenger and our web application on the tigase.im.
	wojciech.kapcia@tigase.net commented 1 decade ago Example: SENT <message to="user1@domain.tld" type="chat"><body>alpha</body><active xmlns="http://jabber.org/protocol/chatstates"/></message> SENT <message to="user1@domain.tld" type="chat"><body>beta</body><active xmlns="http://jabber.org/protocol/chatstates"/></message> SENT <message to="user1@domain.tld" type="chat"><body>charlie</body><active xmlns="http://jabber.org/protocol/chatstates"/></message> RECEIVED <message to="user2@domain.tld" from="user1@domain.tld/resource" xmlns="jabber:client" type="chat"><body>delta</body><active xmlns="http://jabber.org/protocol/chatstates"/></message> RECEIVED <message to="user2@domain.tld" from="user1@domain.tld/resource" xmlns="jabber:client" type="chat"><body>foxtrot</body><active xmlns="http://jabber.org/protocol/chatstates"/></message> RECEIVED <message to="user2@domain.tld" from="user1@domain.tld/resource" xmlns="jabber:client" type="chat"><body>g?</body><active xmlns="http://jabber.org/protocol/chatstates"/></message> SENT <message to="user1@domain.tld" type="chat"><body>golf</body><active xmlns="http://jabber.org/protocol/chatstates"/></message> SENT <iq id="qxmpp433" to="muc.domain.tld" type="get"><unique xmlns="http://jabber.org/protocol/muc#unique"/></iq> RECEIVED <iq id="qxmpp433" from="muc.domain.tld" to="user2@domain.tld/resource" xmlns="jabber:client" type="result"><unique xmlns="http://jabber.org/protocol/muc#unique">nwm7kalohhbxxcm3xyvhgkcsj230oq</unique></iq> SENT <presence to="nwm7kalohhbxxcm3xyvhgkcsj230oq-unique-6b7374657068656e4062726f6164736f66742e636f6d@muc.domain.tld/user2@domain.tld"><x xmlns="http://jabber.org/protocol/muc"/></presence> SENT <iq id="qxmpp435" to="nwm7kalohhbxxcm3xyvhgkcsj230oq-unique-6b7374657068656e4062726f6164736f66742e636f6d@muc.domain.tld" type="get"><query xmlns="http://jabber.org/protocol/muc#admin"><item affiliation="owner"/></query></iq> SENT <iq id="qxmpp436" to="nwm7kalohhbxxcm3xyvhgkcsj230oq-unique-6b7374657068656e4062726f6164736f66742e636f6d@muc.domain.tld" type="get"><query xmlns="http://jabber.org/protocol/muc#admin"><item affiliation="admin"/></query></iq> SENT <iq id="qxmpp437" to="nwm7kalohhbxxcm3xyvhgkcsj230oq-unique-6b7374657068656e4062726f6164736f66742e636f6d@muc.domain.tld" type="get"><query xmlns="http://jabber.org/protocol/muc#admin"><item affiliation="member"/></query></iq> SENT <iq id="qxmpp438" to="nwm7kalohhbxxcm3xyvhgkcsj230oq-unique-6b7374657068656e4062726f6164736f66742e636f6d@muc.domain.tld" type="get"><query xmlns="http://jabber.org/protocol/muc#admin"><item affiliation="outcast"/></query></iq> SENT <message to="user1@domain.tld" type="normal"><x xmlns="jabber:x:conference" continue="true" jid="nwm7kalohhbxxcm3xyvhgkcsj230oq-unique-6b7374657068656e4062726f6164736f66742e636f6d@muc.domain.tld"/></message> SENT <message to="user3@domain.tld" type="normal"><x xmlns="jabber:x:conference" continue="true" jid="nwm7kalohhbxxcm3xyvhgkcsj230oq-unique-6b7374657068656e4062726f6164736f66742e636f6d@muc.domain.tld"/></message>
	Bartosz Małkowski commented 1 decade ago There is protocol for it http://xmpp.org/extensions/xep-0045.html#continue
	Bartosz Małkowski commented 1 decade ago I don't know how they handle two last stanzas in clients, but I think they quietly change normal chat to muc (in client). In this example it seems there is no real history in MUC -- just history in client (no history push). There is protocol for it and I think we should use XEP instead of inventing new one, incompatible with others.
	wojciech.kapcia@tigase.net commented 1 decade ago description updated, removed non-public details
	Bartosz Małkowski commented 1 decade ago Converting a One-to-One Chat Into a Multi-User Conference is implemented already.

Type	New Feature
Priority	Minor
Assignee	wojciech.kapcia@tigase.net
RedmineID	744

Duplicate

#7 Closed

Implement Converting a One-to-One Chat Into a Multi-User Conference

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/tigase-muc#34

Please wait...

Page is in error, reload to recover