On 10/16/10 1:19 AM, Kevin Smith wrote:
> On Thu, Oct 14, 2010 at 3:12 PM, Leon Roy wrote:
>> We're coding new XMPP clients which report to each other the time a message
>> is read by the far party.
>
> At the moment, XEP-0184 is worded ambiguously about whether it deals
> with delivery notificat
On Sun Oct 17 10:13:50 2010, Michael Laukner wrote:
The second is from the CDCIE chat protocol. It's of the form:
I'd note that this one, at least, is actually used much like the
"signing time" explicitly defined in XEP-0285 - and presumably Kurt's
new proposal will have the same.
Would be nice to have a procedural or informational XEP that provides
guidelines or describes Best Practice for time related use cases.
1.) ENTITY TIME: XEP-0202
2.) DELAYED DELIVERY: XEP-0203
3.) TIME STAMP: (see
http://www.mail-archive.com/j...@jabber.org/msg21605.html ). There
seem to be two
On Thu, Oct 14, 2010 at 3:12 PM, Leon Roy wrote:
> We're coding new XMPP clients which report to each other the time a message
> is read by the far party.
At the moment, XEP-0184 is worded ambiguously about whether it deals
with delivery notifications, or read notifications. It's been my
intentio
On 10/15/10 3:20 PM, Waqas Hussain wrote:
> I'd use XEP-0203: Delayed Delivery
>
> That would be because of that 'from' attribute on the
> element, among other things.
Yes, that seems better to me.
Peter
--
Peter Saint-Andre
https://stpeter.im/
smime.p7s
Description: S/MIME Cryptogr
On Thu, Oct 14, 2010 at 7:12 PM, Leon Roy wrote:
> Hello,
>
> We're coding new XMPP clients which report to each other the time a message
> is read by the far party.
>
>
>
> Would extending the element with urn:xmpp:time from XEP-0202 like
> below be valid?
>
>
> from='northumberl...@shakes
Hello,
We're coding new XMPP clients which report to each other the time a message is
read by the far party.
Would extending the element with urn:xmpp:time from XEP-0202 like
below be valid?
from='northumberl...@shakespeare.lit/westminster'
id='richard2-4.1.247'
to='kingric
