Summary: | don't advertise OLPC caps unless OLPC interfaces are used | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Robert McQueen <robert> |
Component: | gabble | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | enhancement | ||
Priority: | medium | CC: | dafydd.harries |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Robert McQueen
2007-11-09 05:02:44 UTC
Doesn't this mean that, when using OLPC stuff, we'll have more traffic? (Send updated presence node with new bundle, resulting caps disco queries?) It would be so bad if Gabble trusted capability bundles with the same node/version as itself. (In reply to comment #1) > Doesn't this mean that, when using OLPC stuff, we'll have more traffic? (Send > updated presence node with new bundle, resulting caps disco queries?) > > It would be so bad if Gabble trusted capability bundles with the same > node/version as itself. Gabble does trust versions and bundles which it's aware of, so no, this will not cause any additional traffic. Any Gabble of an appropriate version that sees http://tfo/xmpp/gabble#olpc will know what it means already. Proposed fix: http://monkey.collabora.co.uk/telepathy-gabble-gadget/ I created another branch containing only this fix: http://monkey.collabora.co.uk/telepathy-gabble-olpc-bundle/ Merged to HEAD. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.