Ticket #4927 enhancement new
twisted.tap.portforward should use string endpoints for listen and destination addresses
| Reported by: | exarkun | Owned by: | tpratt |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | core | Keywords: | |
| Cc: | Branch: | ||
| Author: | tpratt | Launchpad Bug: |
Description
Currently the portforward options are somewhat confusing. There are three of them, two for ports and one for a host. After a little puzzling, it's possible to figure out that host and dest_port define a remote TCP server to forward connections to, while port is a strport description of an address to listen on.
The current naming scheme mixes local with remote making it harder to figure out how to use the tool. But it also limits the forward destination to TCP addresses. It would be great to use endpoints to allow any sort of remote address to be specified. As well, it would be good to update the use of strports to endpoints for the local listening address.
This would be an excellent, simple showcase of the features you get with endpoints.

