Feature #2991
closedFaceManager: specify face persistency
Description
In faces/create
command processing, allow creating a permanent face if the requester asks for FacePersistency::PERMANENT
.
Necessary changes in ndn-cxx ControlParameters
and FaceCreateCommand
is included as part of this issue.
Updated by Junxiao Shi over 9 years ago
- Blocked by Feature #2990: FaceMgmt: specify face persistency added
Updated by Junxiao Shi over 9 years ago
- Blocked by Feature #2989: Minimal UDP permanent face added
Updated by Junxiao Shi over 9 years ago
This is a small change, and MAY be completed without waiting for #2107 completion.
Updated by Junxiao Shi over 9 years ago
- Related to Feature #2993: nfdc: create permanent faces added
Updated by Junxiao Shi over 9 years ago
- Blocks Feature #2994: UDP permanent face scenario added
Updated by Junxiao Shi over 9 years ago
- Description updated (diff)
- Estimated time changed from 2.00 h to 3.00 h
We need to reconsider note-4.
This issue needs to change ControlParameters
which conflicts with the Dispatcher change in #2107.
Updated by Junxiao Shi over 9 years ago
20150821 conference call decides that this doesn't need to wait for Dispatcher
. Yanbiao agrees to resolve conflicts in ControlParameters
when they happen.
Updated by Yukai Tu over 9 years ago
- Status changed from New to In Progress
- Estimated time changed from 3.00 h to 1.00 h
Updated by Yukai Tu over 9 years ago
- Estimated time changed from 1.00 h to 3.00 h
Updated by Alex Afanasyev over 9 years ago
@Yukai Can you finish updating the outstanding commits in gerrit by noon tomorrow? I don't like that we have dragged this issue up until the release (noon tomorrow) and I have to add disclaimer that even though we have support, but one cannot use it because management is missing for now... If you need help, I and other guys will be willing to help.
Updated by Junxiao Shi over 9 years ago
Updated by Yukai Tu over 9 years ago
Can you give me some guides about unit tests under ndn-cxx? Thanks.
Updated by Yukai Tu over 9 years ago
I may need some helps when I doing unit test on ndn-cxx. Here are some error messages:
Running 607 test cases...
../tests/unit-tests/util/dns.t.cpp(59): fatal error in "Asynchronous": Resolved to 92.242.140.2, but should have failed
../tests/unit-tests/util/face-uri.t.cpp(87): error in "CanonizeUdpV4": udp4://invalid.invalid should fail
../tests/unit-tests/util/face-uri.t.cpp(88): error in "CanonizeUdpV4": check tc->m_expectedUri == canonicalUri.toString() failed [ != udp4://92.242.140.2:6363]
../tests/unit-tests/util/face-uri.t.cpp(87): error in "CanonizeTcpV4": tcp4://invalid.invalid should fail
../tests/unit-tests/util/face-uri.t.cpp(88): error in "CanonizeTcpV4": check tc->m_expectedUri == canonicalUri.toString() failed [ != tcp4://92.242.140.2:6363]
How can I fix these errors?
Updated by Junxiao Shi over 9 years ago
Answer to note-15:
You may be using a misbehaving/malicious DNS server.
If there is no other failure, you may ignore these errors.
Updated by Alex Afanasyev over 9 years ago
@Yukai Some ISPs provide "misbehaved" caching DNS resolvers that return bogus IP address of internal "search" engine, instead of failing to resolve the domain name. In my case, TimeWarner did that, so I configured my router's DHCP to use Google's DNS. I guess COX is also doing this.
You can either switch your DNS settings to use different caching resolver or, as Junxiao suggested, ignore these specific errors.
Updated by Junxiao Shi over 9 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100