On an abstract level I feel like using the by attribute for the
Message-ID-XEP will make the XEP more general purpose. Even though we might
not necessarily see a benefit for multiple instances adding their own IDs
now we might have a use case for them in the future.
As for letting the client choos
On 7 June 2015 at 21:39, Florian Schmaus wrote:
> On 07.06.2015 20:42, Georg Lukas wrote:
>> 3) Create a MID generation scheme that can be independently followed by
>> client and server, i.e. full-jid + stream-id + packet-id.
>
> I'd don't think we'll need the full-jid. The properties of the strea
On 07.06.2015 20:42, Georg Lukas wrote:
> 3) Create a MID generation scheme that can be independently followed by
> client and server, i.e. full-jid + stream-id + packet-id.
I'd don't think we'll need the full-jid. The properties of the stream-id
are sufficient to generate a unique, collision free
* Daniel Gultsch [2015-06-05 13:01]:
> And I'm currently not really seeing the point of a client adding an id
> since the client can already set the stanza id.
Besides of the MUC-eating-your-message-ID use case there is another one
that was heavily discussed as a possible motivation for client-id
On 04.06.2015 12:56, Kurt Zeilenga wrote:
> It’s not clear to me that the problems that this extensions proposes to
> address can be addressed through use an extension to XMPP. Extensions
> ought to be truly optional. This ProtoXEP appears to be making mandates
> which are more appropriate made,
On 05.06.2015 13:26, Matthew Wild wrote:
> On 5 June 2015 at 12:07, Daniel Gultsch wrote:
>> 2015-06-05 13:01 GMT+02:00 Daniel Gultsch :
>>>
>>> And I'm currently not really seeing the point of a client adding an id
>>> since the client can already set the stanza id. With an the by attribute we
>>
On 03.06.2015 17:02, XMPP Extensions Editor wrote:
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: Unique and stable message IDs
>
> Abstract: This specification describes unique and stable IDs for message
> stanzas.
>
> URL: http://xmpp.org/extensions/inbox/mid.h
On 5 June 2015 at 12:07, Daniel Gultsch wrote:
>
>
> 2015-06-05 13:01 GMT+02:00 Daniel Gultsch :
>>
>>
>> And I'm currently not really seeing the point of a client adding an id
>> since the client can already set the stanza id. With an the by attribute we
>> don't have to decide on whether or not
2015-06-05 13:01 GMT+02:00 Daniel Gultsch :
>
> And I'm currently not really seeing the point of a client adding an id
> since the client can already set the stanza id. With an the by attribute we
> don't have to decide on whether or not there is a use case for the
> client-id.
>
>
fwiw I just tho
2015-06-04 11:26 GMT+02:00 Matthew Wild :
>
> This revision says that there must only be a single id at any point in
> time. This would prevent you from learning the id that a remote MUC
> service (or any other entity) assigned it (in case you want to query a
> MUC's archive).
>
> I would probably
On 4 June 2015 at 11:56, Kurt Zeilenga wrote:
> For the MAM case, to the extent what it offers in the current Experimental
> XEP is not sufficient, I suggest MAM XEP be modified to provide for reliable
> identification of archived content.
Just so you know, this XEP grew out of MAM because we int
I'm in broad agreement with what Kurt writes below.
I think the only point where we differ is that the "does MUC issue new ids"
question is really one we could answer now (and if not directly answer,
certainly fix).
I would also add that using the stanza's id and from attributes, plus a
(possibly
It’s not clear to me that the problems that this extensions proposes to address
can be addressed through use an extension to XMPP. Extensions ought to be
truly optional. This ProtoXEP appears to be making mandates which are more
appropriate made, if the community were to support them being mad
On 3 June 2015 at 16:02, XMPP Extensions Editor wrote:
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: Unique and stable message IDs
>
> Abstract: This specification describes unique and stable IDs for message
> stanzas.
>
> URL: http://xmpp.org/extensions/inbox/mid
On 3 Jun 2015, at 16:02, XMPP Extensions Editor wrote:
> Title: Unique and stable message IDs
>
> URL: http://xmpp.org/extensions/inbox/mid.html
Hoorah again for short XEPs.
3.1 - I think SHOULD is too strong for UUIDs here, isn’t it? There’s no
interoperability concern - so I’d just go with ‘
15 matches
Mail list logo
