Hi,
On Feb 26, 2008, at 3:15 PM, Joe Hildebrand wrote:
What about section 6.3 of the new version of XEP-115?
<stream:features>
<c xmlns='http://jabber.org/protocol/caps'
hash='sha-1'
node='http://jabberd.org'
ver='ItBTI0XLDFvVxZ72NQElAzKS9sU='>
</stream:features>
Then you don't even have to do the disco, except the first time.
Yes, that would cut down the number of disco's in everything we do,
but I still think putting this information in there is wrong. If we
do this for 157, why not slap the jabber:id:time in there?
The pattern has been: use disco#info to discover support, then use a
IQ GET or something similar to retrieve the information.
And I don't see any reason to break the pattern.
Best regards,
On Feb 26, 2008, at 7:24 AM, Pedro Melo wrote:
Hi,
during the latest DevCon, one of the issues about deployment was
contact addresses. The current XEP for that is 0157.
I think that 157 breaks the current disco#info usage pattern. We
use disco#info to discover which protocols an entity supports, not
the get the information directly (exception for basic <identity
>). So receiving the entire contact information in the disco#info
reply seems wrong, because on most requests, we don't need it.
I think we should use a pubsub node instead. This would give us
all the benefits of pubsub, and we could probably implement this
faster, given that pubsub and pep are starting to get deployed in
latest releases of some servers like Openfire and Ejabberd.
The schema for the information could be reused from XEP-0157 or
XEP-0154 if that one comes back from the dead.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: [EMAIL PROTECTED]
Use XMPP!
--
Joe Hildebrand
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
XMPP ID: [EMAIL PROTECTED]
Use XMPP!
