[Standards-JIG] Re: pubsub: cache-last-item
stpeter at jabber.org
Sat Feb 18 04:10:09 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Pedro Melo wrote:
> On Feb 2, 2006, at 2:08 PM, Kevin Smith wrote:
>> On 2 Feb 2006, at 14:00, Remko Troncon wrote:
>>> On 30 Jan 2006, at 23:28, Peter Saint-Andre wrote:
>>>> 2. When a subscription is accepted/approved, the service SHOULD send
>>>> last published item to the new subscriber.
>>> Related to this, i was wondering how in the avatar use case would
>>> work in SPPS. When you log on with a client, how is the client
>>> supposed to know whether the avatar metadata of its contacts changed
>>> or not ? In the presence-based JEPs, the last hash was automatically
>>> sent with the presence of the roster item, so you got that info every
>>> time. Now, it seems that you have to query every contact at login
>>> time (which isn't really feasible).
>> What we really need is delivery on first presence from a resource.
>> While this isn't interesting for the models the 0060 jep seems to have
>> been aimed at, for IM purposes this, or something like it, is vital,
>> as is delivery to all resources, not only the highest priority.
> After talking with Kevin about this, and given that we at Sapo are also
> implementing SPPS on our client, this issue is very important and it
> would simplify greatly our client.
IIRC, Kevin and I added this to version 0.4 of JEP-0163.
> Another idea that we talked about: if the SPPS receives my presence with
> caps, it would be nice if he only sends the last published item for the
> protocols we support... That would be excellent for users that use both
> a mobile client (less caps) and a desktop client (full caps) as it would
> allow the SPPS broadcast to be tailored to the real capabilities of the
Ah, that's a smart optimization. In fact the PEP service could also
determine if a resource supports JEP-0163 and not send the notification
if the resource is a "dumb client". I'll add something about that to the
next version of JEP-0163.
Jabber Software Foundation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards