#3683 NORM First D: Long XO Names break presence/mesh
Zarro Boogs per Child
bugtracker at laptop.org
Mon Sep 24 14:13:16 EDT 2007
#3683: Long XO Names break presence/mesh
-------------------------------+--------------------------------------------
Reporter: BigBaaadBob | Owner: smcv
Type: defect | Status: assigned
Priority: normal | Milestone: First Deployment, V1.0
Component: presence-service | Version:
Resolution: | Keywords:
Verified: 0 |
-------------------------------+--------------------------------------------
Changes (by smcv):
* owner: sjoerd => smcv
* status: new => assigned
* component: telepathy-salut => presence-service
Comment:
The instance name in Salut can be up to 63 characters (limited by the mDNS
protocol, so this is out of our control). Chrysanthemum at xo-12-34-56 is 25
characters, and for activities, Salut tries to advertise
activityidactivityid:Chrysanthemum at xo-12-34-56 (where activityidactivityid
represents a 40-character hex activity ID, as currently implemented). This
is *just* too long, so it fails.
We could work around this in Presence Service by truncating the nickname
part of the instance name to 10 characters (Chrysanthemum is 13
characters). This isn't the nickname seen on the mesh view, which will be
unaffected - it's just the instance name that will be seen in generic mDNS
debug tools and possibly a few non-Telepathy link-local-XMPP clients - so
I think this is an acceptable workaround.
The longer-term fix would be to stop having to have the instance name in
the activity advertisement, which will require some upstream Avahi fixes
(and will also break interoperability with older XOs on the mesh, so
ideally we should do this at the same time as some other incompatible
protocol change, like the rMulticast change represented by the salut-
needs-new-protocol keyword).
--
Ticket URL: <https://dev.laptop.org/ticket/3683#comment:9>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list