Feature #2189
closed
Pick Transport type with client.conf
100%
Description
Add a transport option to client.conf.
Its value is a FaceUri that represents a listener. This FaceUri does not have to be canonical.
To pick UnixTransport: transport=unix:///var/run/nfd.sock
Path can be changed if necessary.
To pick TcpTransport: transport=tcp://localhost:6363
Port can be changed if necessary.
"tcp://localhost" is recommended; other variants such as "tcp4://127.0.0.1" or "tcp6://[::1]" is acceptable but not recommended.
Connecting to a non-local endpoint is unsupported but not forbidden.
The default constructor of Face class should respect this configuration, instead of always creating UnixTransport.
Updated by Junxiao Shi about 10 years ago
- Related to Bug #2188: FaceManager creates UnixStreamChannel when listen=no added
Updated by Junxiao Shi about 10 years ago
- Blocks Bug #2190: NRD cannot start when NFD disables UNIX faces added
Updated by Junxiao Shi about 10 years ago
- Related to deleted (Bug #2188: FaceManager creates UnixStreamChannel when listen=no)
Updated by Anonymous about 10 years ago
- Status changed from New to In Progress
- Assignee set to Anonymous
Updated by Junxiao Shi about 10 years ago
I want to point out that this Feature lacks design approval. If you go implement it, there's risk of having to rework everything in case design is rejected.
Updated by Anonymous about 10 years ago
What do you thinking of changing to use Face URIs to specify the protocol, host, and port? Handling Unix transport without a Face URI is trivial, but I'd hate to replicate existing functionality to determine whether a TCP/UDP host option was IPv4, v6, or a hostname.
To pick UnixTransport:
transport=unix:///var/run/nfd.sock
To pick IPv4 TcpTransport:
transport=tcp4://localhost:6363
Updated by Junxiao Shi about 10 years ago
- Description updated (diff)
I agree with the design in note-7.
Updated by Anonymous almost 10 years ago
- Status changed from In Progress to Code review
- % Done changed from 0 to 70
Updated by Anonymous almost 10 years ago
Where can I find the ndn-cxx documentation that needs to be updated? Is it a separate repo or something under docs?
Updated by Alex Afanasyev almost 10 years ago
- Status changed from Code review to In Progress
Updated by Junxiao Shi almost 10 years ago
Where can I find the ndn-cxx documentation that needs to be updated? Is it a separate repo or something under docs?
It's a separate repository. http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-December/000673.html
Updated by Anonymous almost 10 years ago
- Status changed from In Progress to Code review
- % Done changed from 70 to 100
Added text to internals describing client.conf and comments are appreciated. I will close the issue in a few days if there are no suggestions.
Updated by Junxiao Shi almost 10 years ago
- Status changed from Code review to Closed
I have reviewed ndn-cxx-docs commit f6d632cc8b923a3e6c497d463c6a93a7b45607b8.
Updated by Junxiao Shi almost 10 years ago
- Related to Bug #2360: Multiple scenarios: ERROR: error while connecting to the forwarder (No such file or directory) added