jabber:x:delay
Messages are sometimes sent to
entities that aren’t available at that particular
moment. If they are stored offline, they are timestamped, in the
jabber:x:delay namespace, so that when they are
finally received, the recipient can use this information to determine when
they were originally sent:
RECV: <message to='sabine@yak/Work' from='yak'>
<subject>Weekend at last!</subject>
<body>Don't forget Father's Day on Sunday!</body>
<x xmlns='jabber:x:delay' from='yak/announce/motd'
stamp='20010615T09:00:01'>Announced</x>
</message>
In this Message-Of-The-Day (MOTD) announcement, we see that, as well as
the stamp attribute showing that the announcement
was sent out on the Friday morning before Father’s Day, a short
text description, “Announced”, is included.
The namespace is also used by the xdb component to
timestamp various fragments of data stored in the user’s records on the
server. Here, we see that Sabine updated
her user registration details (using a jabber:iq:register
query during her session) at the beginning of March:
<query xmlns='jabber:iq:register' xdbns='jabber:iq:register'> <name>S. Reitz-Adams</name> <email>sabine@reitz-adams.org</email> <x xmlns='jabber:x:delay' stamp='20010302T12:15:42'>updated</x> </query>
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access