Guillaume Desmottes wrote: > Can you tell me exactly what happen in this scenario from a Telepathy > pov? > > activity is opened and shared: > - You create a new muc room and join > - You request a tubes channel > - You offer a tube on this channel (D-Bus? Stream?)
D-Bus > activity is closed: > - You close the muc room and so the tubes channel and the tube > > Is that correct? I'm not sure. I mean to say: participant A launched an activity, and then shared it, which created a D-Bus tube. Participant B joined the shared activity, and correctly received the tube. The two participants were able to communicate correctly over this tube. Then participant A left the shared activity, but B remained. Participant A then relaunched the shared session from the Journal. (It's not possible to rejoin the shared session from the Neighborhood view, because of http://dev.sugarlabs.org/ticket/934.) > What happen when the activity is relaunched from the Journal? > - You rejoin the same room? > - Does it still contain participants? > - Are you offering a new tube? I am not offering a new tube. I think I'm joining the same room, with participant B still inside, but I am not sure. > If the Journal doesn't explicitly re-offer the tube, there are different > scenarios: ... > - Tube was a D-Bus one and some people were still in the tube when you > left and rejoin. Then the tube still exists. This is the scenario that I expect to be in. > Does that make sense to you? Yes. Another point I should make is: this "re-joining" behavior works fine for the Chat activity, which avoids ListTubes altogether. Unfortunately, Chat uses the Telepathy API in a way that I do not understand. >> First, the Presence Service confirms that there is a Tubes channel: >> >> DEBUG sugar.presence.activity: <proxy for >> /org/laptop/Sugar/Presence/Activities/17 at b5f04f2c>: Connection >> <telepathy.client.conn.Connection object at 0xb5f0814c> is ready >> DEBUG sugar.presence.activity: <proxy for >> /org/laptop/Sugar/Presence/Activities/17 at b5f04f2c>: Text channel >> <telepathy.client.channel.Channel object at 0xb5f0832c> is ready >> DEBUG sugar.presence.activity: <proxy for >> /org/laptop/Sugar/Presence/Activities/17 at b5f04f2c>: Tubes channel >> <telepathy.client.channel.Channel object at 0xb5f083ec> is ready >> DEBUG sugar.presence.activity: <proxy for >> /org/laptop/Sugar/Presence/Activities/17 at b5f04f2c>: finished setting up >> tubes >> DEBUG root: Share of activity 47298b3119f10cbdc7ac3d9971971b19a5e01dfb >> successful, PS activity is <proxy for >> /org/laptop/Sugar/Presence/Activities/17 at b5f04f2c>. >> >> but when my code asks for tube, using the ListTubes API, ListTubes replies >> to its reply_handler with an empty list: >> >> DEBUG org.sugarlabs.SharedTextDemo: This is not my activity: waiting for a >> tube... >> ... >> DEBUG org.sugarlabs.SharedTextDemo: Got 0 tubes from ListTubes. >> >> What's going on here? >> >> Thanks, >> Ben >> >> P.S. This is all in Sugar 0.82, OLPC OS 8.2.0, using (I think) Telepathy >> 0.15.0. > > > Are you testing using Gabble or Salut? Shouldn't make any difference but > that's always good to know. > > > Hope that helps, > > > G. > > _______________________________________________ > telepathy mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/telepathy
signature.asc
Description: OpenPGP digital signature
_______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
