Task #1918
closedDNS resolver
100%
Description
Develop a utility class to perform DNS resolution, including sync and async modes.
Code from NFD resolver.hpp can be reused.
Updated by Junxiao Shi about 10 years ago
I believe ndn-cxx should provide a routine for FaceUri canonization, which includes DNS resolution when necessary.
Updated by Alex Afanasyev about 10 years ago
That could be another utility class
Updated by Alex Afanasyev about 10 years ago
- Blocks Task #1911: Create face with canonical FaceUri added
Updated by Junxiao Shi about 10 years ago
- Blocks Task #1909: nfdc: ensure FaceUri is in canonical form added
Updated by Junxiao Shi about 10 years ago
Boost.Asio has ip::udp::resolver
and ip::tcp::resolver
types.
The only difference I can imagine is that they can parse textual port number differently (eg. TCP port "www" is port 80).
I don't think this feature is necessary, because FaceUri
never allows textual port numbers.
Therefore, the DNS resolver utility class could use only ip::udp::resolver
, and support only hostname resolution.
Updated by Junxiao Shi about 10 years ago
- Subject changed from Incorporate DNS resolver as a new utility class to DNS resolver
- Description updated (diff)
Updated by Junxiao Shi about 10 years ago
- Blocks Task #1994: FaceUri canonization added
Updated by Junxiao Shi about 10 years ago
- Blocks deleted (Task #1911: Create face with canonical FaceUri)
Updated by Junxiao Shi about 10 years ago
- Blocks deleted (Task #1909: nfdc: ensure FaceUri is in canonical form)
Updated by Vince Lehman about 10 years ago
I am unable to change the status to in progress, but I have started working on this.
Updated by Vince Lehman about 10 years ago
- Status changed from New to In Progress
Updated by Vince Lehman about 10 years ago
- Status changed from In Progress to Code review
- % Done changed from 0 to 90
Updated by Junxiao Shi about 10 years ago
- Status changed from Code review to Closed
- % Done changed from 90 to 100