[tahoe-lafs-trac-stream] [tahoe-lafs] #1086: servers should attempt to open connections to clients

[tahoe-lafs]

#1086: servers should attempt to open connections to clients
------------------------------+----------------------------
     Reporter:  zooko         |      Owner:
         Type:  enhancement   |     Status:  new
     Priority:  major         |  Milestone:  eventually
    Component:  code-network  |    Version:  1.7β
   Resolution:                |   Keywords:  introducer p2p
Launchpad Bug:                |
------------------------------+----------------------------
Changes (by zooko):

 * keywords:  introducer => introducer p2p


Old description:

> Currently each client attempts to open a connection to each server. If it
> were the case that a server were behind NAT or firewall and connections
> couldn't be opened to that server, but that server were able to open
> connections out to clients, then if it did so the clients would be able
> to use that connection to issue requests to the server.
>
> To do this, servers should ask the introducer(s) to tell them about all
> clients and then servers should attempt to establish a foolscap
> connection to each client. If there is already such a connection
> (because, for example the client has already opened a connection to the
> server) then foolscap will automatically deduplicate and keep just one
> working connection.

New description:

 Currently each client attempts to open a connection to each server. If it
 were the case that a server were behind NAT or firewall and connections
 couldn't be opened to that server, but that server were able to open
 connections out to clients, then if it did so the clients would be able to
 use that connection to issue requests to the server.

 To do this, servers should ask the introducer(s) to tell them about all
 clients and then servers should attempt to establish a foolscap connection
 to each client. If there is already such a connection (because, for
 example the client has already opened a connection to the server) then
 foolscap will automatically deduplicate and keep just one working
 connection.

--

Comment:

 adding keyword {{{p2p}}} to tag tickets that have to do with the open
 question of "Is Tahoe-LAFS client-server or is it peer-to-peer?":
 [//pipermail/tahoe-dev/2012-July/007533.html]

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1086#comment:15>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage