[Telepathy] File transfer spec: need for advice

[Marco Barisione]

Il giorno mer, 22/08/2007 alle 15.12 +0100, Simon McVittie ha scritto:
> For reference: there is another issue with the spec, which is that it
> should use the same mechanisms for local-socket access control (and
> probably protocol selection) that Tubes do, and we haven't written that
> part of the Tubes spec yet. I'll try to get that done early next week.

Now we have the tubes spec, what should I do for file transfer?
Currently in the ft spec we have only non-abstract Unix sockets, do we
need to support other socket type? IMO Unix sockets (both abstract and
non-abstract) are enough, later we can add Windows named pipes.

To support multiple socket types we can add
GetAvailable(Stream)?FileTransferTypes () -> a{uau}, returning
something like:

{
    Socket_Address_Type_Unix:
        [Socket_Access_Control_Localhost,
         Socket_Access_Control_Credentials],
    Socket_Address_Type_Abstract_Unix:
        [Socket_Access_Control_Localhost,
         Socket_Access_Control_Credentials]
}

Then GetLocalUnixSocketPath( u: id) -> ay can become
GetLocalUnixSocketPath ( u: id ) -> u, ay, where the uint is
Socket_Address_Type_Unix or Socket_Address_Type_Abstract_Unix.

Another option is to be more generic and replace
GetLocalUnixSocketPath() with a
Get(Stream)?FileTransferSocketAddress() method, similar to
GetStreamTubeSocketAddress().

What do you think?

-- 
Marco Barisione
http://www.barisione.org/