Hi,
So currently we have XEP-0012 which we don't like because of the relative
time semantic, it uses. In addition that it is currently used for two
different purposes:
1. Discover the time a disconnected user last accessed its account (i.e.
was online).
2. Discover when a connected user was last
So currently we have XEP-0012 which we don't like because of the relative time
semantic, it uses. In addition that it is currently used for two different
purposes:
1. Discover the time a disconnected user last accessed its account (i.e. was
online).
which is solved by
Folks,
It looks like purge_offline's behaviour in XEP-0060 is entirely
undefined. The pertinent bits seem to be:
1) That purge_offline means: Whether to purge all items when the
relevant publisher goes offline
2) That, when talking about a normal purge a purge request MUST NOT
result in
On 2013-02-18 17:34, Kevin Smith wrote:
Folks,
It looks like purge_offline's behaviour in XEP-0060 is entirely
undefined. The pertinent bits seem to be:
1) That purge_offline means: Whether to purge all items when the
relevant publisher goes offline
2) That, when talking about a normal
Attached is a proposed patch to de-recommend HTTP pipelining, as discussed at
the summit. Critiques welcome!
/me moves onto 1 sometimes 2 sockets
- mm
Matthew A. Miller
http://goo.gl/LK55L
pipelining.patch
Description: Binary data
On 02/18/2013 09:18 AM, Tobias Markmann wrote:
Hi,
So currently we have XEP-0012 which we don't like because of the
relative time semantic, it uses. In addition that it is currently used
for two different purposes:
1. Discover the time a disconnected user last accessed its account
(i.e. was
In addition that it is currently used for two different purposes:
Actually, it looks like three purposes: time since last online, idle time
(clients), and current uptime (servers/components).
2. Discover when a connected user was last active at the server. (The XEP
calls it idle time,
On 15/02/2013 22:42, Dave Cridland d...@cridland.net wrote:
Yes, but jid and node, please. Might not be a server as such.
Very good point :)
iq type='set' from='rainbowd...@mlp.net' id='sub123'
pubsub xmlns='http://jabber.org/protocol/pubsub'
publish node='urn:xmpp:pubsub:subscription'
