On Jan 23, 2013, at 3:42 PM, Tobias Markmann <[email protected]> wrote:
> Hi, > > kind of as follow up post to my recent lone message here a more general > approach to the problem. > > How about adding an optional attribute to XEP-0012's query stanza (eg. > stamp) for indicating absolute time. Depending on what you use the time for > you might require the entities in XMPP to be synced in time. This would be > backward-compatible, by still requiring seconds attribute and having an > optional stamp attribute. So it would look like: > > <query xmlns='jabber:iq:last' seconds='903' stamp='2012-09-10T23:41:07Z' /> > > > With relative time, the only way to do it now, to get absolute time you > either have to ping the remote party for its current time (+ transmission > delay) or use your own time. Either way you get something but probably not > the actual absolute time of the described event. > > Thoughts? Opinions? > > Cheers, > Tobi To be clear, 'stamp' is the equivalent of 'seconds', in absolute terms. The recipient wouldn't deduct 'seconds' from 'stamp' to get the ultimate result. Also, would 'stamp' always be in terms of UTC, or are other offsets permitted? I can see pros and cons for both sides of that fence. I've got no objections to this proposal, and it seems to meet the threshold for a Final XEP. - m&m Matthew A. Miller < http://goo.gl/LK55L >
smime.p7s
Description: S/MIME cryptographic signature
