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/[email protected]/msg21605.html ). There seem to be two timestamp approaches for XMPP. The first is in "Stanza Headers and Internet Metadata" [XEP-0131]. <headers xmlns='http://jabber.org/protocol/shim'> <header name='Created'>2004-09-21T03:01:52Z</header> </headers> The second is from the CDCIE chat protocol. It's of the form: <x xmlns='jabber:x:tstamp' tstamp="CCYY-MM-DDThh:mm:ss.sssZ/> For example: <x xmlns='jabber:x:tstamp' tstamp="2008-03-10T12:43:18.002Z/> 4.) MESSAGE RECEIPT: XEP-0184 5.) TIME-TO-LIVE: XEP 0079 “Advanced Message Processing”: time-to-live (TTL) and reliability-in-delivery features for chat. 6.) Server TIME SYNCING using NTP? Michael On Sat, Oct 16, 2010 at 9:19 AM, Kevin Smith <[email protected]> wrote: > On Thu, Oct 14, 2010 at 3:12 PM, Leon Roy <[email protected]> wrote: >> We're coding new XMPP clients which report to each other the time a message >> is read by the far party. >
