-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/17/09 6:15 AM, Fabio Forno wrote: > On Thu, Sep 17, 2009 at 9:14 AM, Pedro Melo <[email protected]> wrote: >> Hi, > >> No. I would need to check the previous versions but I *almost* certain that >> XEP-0030 disco-publish feature was created to help clients deal with the >> initial storm of disco#info requests. Basically, a client would publish his >> disco#info information to the server, and from then on, any requests for >> that information from other clients would be replied by the server, and not >> the client. > >> Like a HTTP proxy cache, with the twist that the HTTP server would push the >> latest version of the document to the proxy. >> >> Others might know the true reason for that part of the spec, I can only >> speculate. Maybe it was written to solve the initial thundering herd of >> disco#info requests from everybody on your roster when you log in. Right >> now, I think the latest XEP-0115 (after we solve the pre-image attacks) is a >> better solution. >> > > Well this is good for di...@info, but what about disco#items?
The old disco-publish stuff was for items, not info (since info can be handled already via entity capabilities). The motivating use case was chatroom services, where rooms are being created and destroyed on a regular basis (which you won't know about unless you can receive a push of some kind). Defined here: http://xmpp.org/extensions/attic/xep-0030-2.3.html#publish > Publishing new items to pubsub nodes seems reasonable to me, since it > would allow caching that information in the client (for example we do > extensive use of ad hoc commands in our client and it would be nice to > be able to cache that information an be notified only when it's > changed). > Since the distribution of disco#items follows a pattern where there > is only one publisher some like PEP could be ideal. > (there is just the problem that with many services like muc you don't > have presence subscriptions) But they could have temporary presence sharing. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqyObYACgkQNL8k5A2w/vyT8ACdGk6u5L/8+9qOZIdWkOHxDhmA +J0An01haDPDAHl7ROS8OlGWYKP1gG8r =GceE -----END PGP SIGNATURE-----
