On 1 April 2015 at 18:33, Matthew Wild mwi...@gmail.com wrote:
On 1 April 2015 at 17:37, Dave Cridland d...@cridland.net wrote:
Folks,
Matthew Miller and Joe Hildebrand's Carbons XEP has been unchanged for 18
months, and represents a useful and well-deployed protocol, implemented in
most
On 02.04.2015 10:08, Dave Cridland wrote:
On 1 April 2015 at 18:33, Matthew Wild mwi...@gmail.com
mailto:mwi...@gmail.com wrote:
On 1 April 2015 at 17:37, Dave Cridland d...@cridland.net
mailto:d...@cridland.net wrote:
It is also not clear to me what, exactly, the more
I was just typing a reply, but Florian hit the same points as I was
going to, so reply inline...
On 2 April 2015 at 09:35, Florian Schmaus f...@geekplace.eu wrote:
On 02.04.2015 10:08, Dave Cridland wrote:
On 1 April 2015 at 18:33, Matthew Wild mwi...@gmail.com
mailto:mwi...@gmail.com
Hi Matthieu,
On 2 April 2015 at 19:52, Matthieu Rakotojaona
matthieu.rakotoja...@gmail.com wrote:
So I was thinking: what if MAM allowed some kind of long polling, the
way HTTP has popularized it, to accomodate for the online case ?
A client would send
iq type='set' id='juliet1'
query
On 2 April 2015 at 11:07, Kevin Smith kevin.sm...@isode.com wrote:
On 2 Apr 2015, at 10:16, Matthew Wild mwi...@gmail.com wrote:
- Other types beyond 'chat'.
Seems to be something we want to have. And I would tend to put this into
the carbons XEP too.
I'm undecided about this. I
On 1 Apr 2015, at 17:37, Dave Cridland d...@cridland.net wrote:
Folks,
Matthew Miller and Joe Hildebrand's Carbons XEP has been unchanged for 18
months, and represents a useful and well-deployed protocol, implemented in
most (if not all) of the mainstream servers.
Mobile and Desktop
On 2 Apr 2015, at 10:16, Matthew Wild mwi...@gmail.com wrote:
- Other types beyond 'chat'.
Seems to be something we want to have. And I would tend to put this into
the carbons XEP too.
I'm undecided about this. I think we could get away with just saying
that normal+chat should be
On 2 Apr 2015, at 09:08, Dave Cridland d...@cridland.net wrote:
iq type='set'
enable xmlns='urn:xmpp:carbons:2' adv:xmlns='urn:xmpp:carbons:advanced:0'
adv:reflection/
adv:archive-id/
adv:msgtype type='groupchat'/
adv:msgtype type='normal'/
adv:msgtype type='chat'/
/enable
/iq
This
Excerpts from Kevin Smith's message of 2015-04-02 11:07:57 +0100:
On 2 Apr 2015, at 10:16, Matthew Wild mwi...@gmail.com wrote:
- Other types beyond 'chat'.
Seems to be something we want to have. And I would tend to put this
into the carbons XEP too.
I'm undecided about
Folks,
Matthew Miller and Joe Hildebrand's Carbons XEP has been unchanged for 18
months, and represents a useful and well-deployed protocol, implemented in
most (if not all) of the mainstream servers.
Mobile and Desktop clients alike appear to implement this widely.
I appreciate that the last
Seconded.
On 1 April 2015 at 13:37, Dave Cridland d...@cridland.net wrote:
Folks,
Matthew Miller and Joe Hildebrand's Carbons XEP has been unchanged for 18
months, and represents a useful and well-deployed protocol, implemented in
most (if not all) of the mainstream servers.
Mobile and
I appreciate the idea, that it should advance to Draft.
I’ve implemented it in Openfire and didn’t saw any major flaws in the spec.
However, while I did, I often thought „why is it restricted to chat-type only?“.
I think enhancing it to „normal“ messages is a good idea, e.g. to let
On 1 April 2015 at 17:37, Dave Cridland d...@cridland.net wrote:
Folks,
Matthew Miller and Joe Hildebrand's Carbons XEP has been unchanged for 18
months, and represents a useful and well-deployed protocol, implemented in
most (if not all) of the mainstream servers.
Mobile and Desktop
On 1 April 2015 at 17:37, Dave Cridland wrote:
poor timing :-)
+1
- Other types beyond 'chat'.
see http://mail.jabber.org/pipermail/standards/2014-August/029100.html
14 matches
Mail list logo
