#4047 NORM Future : Use peer-to-peer connections for Gabble stream tubes whenever possible (was: Implement one-to-one tubes in gabble with peer-to-peer connections)
Zarro Boogs per Child
bugtracker at laptop.org
Thu Oct 18 11:23:54 EDT 2007
#4047: Use peer-to-peer connections for Gabble stream tubes whenever possible
-------------------------------+--------------------------------------------
Reporter: kimquirk | Owner: smcv
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: telepathy-gabble | Version:
Resolution: | Keywords:
Verified: 0 |
-------------------------------+--------------------------------------------
Comment(by smcv):
I don't think the Telepathy spec means the same thing you do by "one-to-
one tubes", so retitling to avoid confusion. Please follow up if I'm wrong
about the meaning of this bug.
I'm assuming that this bug is a request for improvements to stream tubes.
Instead of using D-Bus tubes, activities can choose to use TCP-ish stream
tubes, in which one participant "exports" a listening (server) socket and
everyone else can connect to it. Currently Gabble implements this, but
Salut doesn't (#4241). The improvement represented by this bug is to use a
direct TCP connection between participants if possible, instead of sending
the data through the server.
Possible implementation A:
1. Implement OOB (out of band) bytestreams in Gabble
2. Implement a fallback mechanism by which OOB is used if possible, and
IBB (the current in-band bytestreams) are used otherwise - Rob thinks Psi
has implemented a suitable technique for file transfer, so this needs
researching
Possible implementation B:
1. Implement pseudo-TCP over UDP using Jingle and libnice
2. Implement a Stream Initiation mechanism using this pseudo-TCP
--
Ticket URL: <https://dev.laptop.org/ticket/4047#comment:1>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list