[Telepathy] Spec for file-transfer and tubes

mikhail.zabaluev at nokia.com mikhail.zabaluev at nokia.com
Thu Mar 15 01:57:01 PDT 2007


>-----Original Message-----
>From: telepathy-bounces at lists.freedesktop.org 
>[mailto:telepathy-bounces at lists.freedesktop.org] On Behalf Of 
>ext Naba Kumar
>Sent: Thursday, March 15, 2007 10:18 AM
>To: Dafydd Harries
>Cc: telepathy at lists.freedesktop.org
>Subject: Re: [Telepathy] Spec for file-transfer and tubes
>On Mon, 2007-03-12 at 15:19 +0000, Dafydd Harries wrote:
>> What about the role of Mission Control in handling tubes? When a tube
>> negotiation channel appears, which application should it 
>launch? It can't
>> really make a useful decision until it knows what kind of 
>tube is being
>> offered, and if this application gets started by Mission 
>Control, it's going
>> to need to be able to recober the state of the tube.
>We will also need to define 'tube details' such that each tube can be
>identified and directed to appropriate client. Very much like 
>mime type,
>except the details are defined by originating client rather then being
>implicit in data content. Also it would need to be free form text (but
>with some agreed format) and not fixed defines.
>This is important for example when we want specialized client
>applications to directly negotiate tubes with remote user's
>corresponding client applications (e.g. networked blackjack game, photo
>shaing etc.). MC can easily, based on the 'details', redirect the tubes
>to any arbitrary client that happen to register for them.

Be aware of the security risks posed by a remote party being allowed to tell what to launch locally.
With MIME types, you can invent your own vendor-specific types as you like.


More information about the Telepathy mailing list