Opened 8 years ago

Closed 8 years ago

#260 closed task (fixed)

expose DefaultTCP in a stable place

Reported by: Brian Warner Owned by:
Priority: major Milestone: 0.12.0
Component: packaging Version: 0.9.1
Keywords: Cc:

Description

It's useful for Tahoe to have access to the DefaultTCP connection-hint handler, to enable an internal Tub-configuration pattern in which all hint-handlers are removed, then a fixed list of new ones are re-installed, including (most of the time) DefaultTCP.

I don't want application code importing DefaultTCP from it's current location, nor from foolscap.pb.

So the task for this ticket is to either expose foolscap.api.DefaultTCP, or to create a new package (maybe foolscap.connections or foolscap.handlers) and expose it in some module in that package.

Exposing it in a package would improve parallelism with the #242 / #246 SOCKS / Tor handlers, so they could all be exposed in the same package. It's important to not put them in the same module (file), however, nor to have the SOCKS/Tor handlers imported by anything else by default, because those handlers will depend upon optional packages like txtorcon and txsocksx, which might not be installed.

Change History (1)

comment:1 Changed 8 years ago by Brian Warner

Resolution: fixed
Status: newclosed

Closed in [8b857d52] by adding foolscap.connections.tcp.DefaultTCP.

Note: See TracTickets for help on using tickets.