On 26 July 2014 12:30, Georg Lukas ge...@op-co.de wrote:
3) In practice, nobody is relying on the uniqueness of 'id's anyway,
because there are so many broken implementations out there.
Two small points on this.
Firstly, many of your other comments rely on the uniqueness and stability
of
On Jul 26, 2014, at 7:43 AM, Dave Cridland d...@cridland.net wrote:
On 26 July 2014 12:30, Georg Lukas ge...@op-co.de wrote:
3) In practice, nobody is relying on the uniqueness of 'id's anyway,
because there are so many broken implementations out there.
Two small points on this.
* Dave Cridland d...@cridland.net [2014-07-26 17:09]:
Firstly, many of your other comments rely on the uniqueness and stability
of ids. An example is your (7) - this relies on all messages sent from the
same occupant jid having unique ids. You'll probably realise some problems
with this
On 26 July 2014 16:53, Kurt Zeilenga kurt.zeile...@isode.com wrote:
On Jul 26, 2014, at 7:43 AM, Dave Cridland d...@cridland.net wrote:
This doesn't invalidate your arguments entirely, but it may well suggest
that RFC 6120 has a technical flaw that needs addressing.
That RFC 6120 text is
Hi,
XEP-0045, section 7.4 http://xmpp.org/extensions/xep-0045.html#message
states:
Note well that for tracking purposes this service assigns a new 'id' to
each message it generates (here using a UUID as defined in RFC 4122 [18]).
I suggest changing that line to:
The service SHOULD reflect the
On Fri, Jul 25, 2014 at 3:06 PM, Georg Lukas ge...@op-co.de wrote:
XEP-0045, section 7.4 http://xmpp.org/extensions/xep-0045.html#message
states:
Note well that for tracking purposes this service assigns a new 'id' to
each message it generates (here using a UUID as defined in RFC 4122 [18]).
On Fri, Jul 25, 2014 at 10:06 AM, Georg Lukas ge...@op-co.de wrote:
Hi,
XEP-0045, section 7.4 http://xmpp.org/extensions/xep-0045.html#message
states:
Note well that for tracking purposes this service assigns a new 'id' to
each message it generates (here using a UUID as defined in RFC 4122
Am 25.07.2014 um 09:22 schrieb Kevin Smith:
On Fri, Jul 25, 2014 at 3:06 PM, Georg Lukas ge...@op-co.de wrote:
XEP-0045, section 7.4 http://xmpp.org/extensions/xep-0045.html#message
states:
Note well that for tracking purposes this service assigns a new 'id' to
each message it generates (here
While I understand your rationale, I think it's counter to the rationale of why
XEP 45
allows MUC services to generate their own id= attributes on stanzas they
forward.
As Waqas noted, the id= produced by the subscriber's client may simply not meet
the
services need for tracking. A service
On Fri, Jul 25, 2014 at 6:08 PM, Philipp Hancke
fi...@goodadvice.pages.de wrote:
Am 25.07.2014 um 09:22 schrieb Kevin Smith:
On Fri, Jul 25, 2014 at 3:06 PM, Georg Lukas ge...@op-co.de wrote:
XEP-0045, section 7.4 http://xmpp.org/extensions/xep-0045.html#message
states:
Note well that for
On 25 July 2014 18:24, Kevin Smith ke...@kismith.co.uk wrote:
On Fri, Jul 25, 2014 at 6:08 PM, Philipp Hancke
fi...@goodadvice.pages.de wrote:
Am 25.07.2014 um 09:22 schrieb Kevin Smith:
On Fri, Jul 25, 2014 at 3:06 PM, Georg Lukas ge...@op-co.de wrote:
XEP-0045, section 7.4
11 matches
Mail list logo
