Opened 15 years ago

Closed 9 years ago

#137 closed enhancement (wontfix)

Tub.listenOn(portfile=)

Reported by: Brian Warner Owned by:
Priority: major Milestone: undecided
Component: usability Version: 0.4.1
Keywords: Cc:

Description (last modified by Brian Warner)

It would be handy to have a portfile= argument to Tub.listenOn(), just like Tub(certFile=) and Tub.registerReference(furlFile=). This would simplify the Tahoe and flappserver setup code that tries to handle port=0 (by saving the kernel-assigned port number in a file, and then re-using it on later invocations).

Attachments (1)

137.diff (7.1 KB) - added by Brian Warner 15 years ago.
starting point for this feature

Download all attachments as: .zip

Change History (3)

comment:1 Changed 15 years ago by Brian Warner

Milestone: 0.5.0undecided

I'm still trying to figure out how this would work, exactly. The last time I looked at it, I got myself confused as to which port number specification should be dominant, and how to handle things like "tcp:0:interface=127.0.0.1".

Changed 15 years ago by Brian Warner

Attachment: 137.diff added

starting point for this feature

comment:2 Changed 9 years ago by Brian Warner

Description: modified (diff)
Resolution: wontfix
Status: newclosed

I'm giving up on this one: we're moving towards more static and less automatic/magic. So I want applications to decide on a port externally, then pass it in to Tub.listenOn(), rather than having Foolscap manage the port allocation and persistence.

#252 is related.

Note: See TracTickets for help on using tickets.