Activity
From 07/02/2017 to 07/31/2017
07/31/2017
- 03:23 PM Task #4196 (Code review): chronosync::Socket::OnDataTimeout does not reset nonce before retransmitting the Interest
- 02:56 PM Bug #4209 (Code review): ChronoSync should not process exclude interests
07/28/2017
- 05:55 PM Task #4195 (Closed): ChronoSync cannot compile after ndn-cxx switch to v2::KeyChain
- 05:55 PM Task #4090 (Closed): Urgent bugs caused by ndn-cxx change 3547
- 09:10 AM Bug #4209 (Closed): ChronoSync should not process exclude interests
- Exclude interests are meant to fetch data from cache.
https://redmine.named-data.net/issues/4179#note-3
07/21/2017
- 03:11 PM Task #2476 (Closed): Update the building instruction to accommodate power-constrained platform
- 03:10 PM Task #2475 (Closed): Remove unnecessary dependency on protobuf
- 03:09 PM Task #2076 (Closed): Reset Interest and sync interest may not arrive in order
07/20/2017
- 03:13 PM Task #4196 (Closed): chronosync::Socket::OnDataTimeout does not reset nonce before retransmitting the Interest
- This may cause the retransmitted Data Interest to be suppressed by NFD.
- 03:09 PM Task #4195 (Closed): ChronoSync cannot compile after ndn-cxx switch to v2::KeyChain
- chronosync::Socket and chronosync::Logic still use "signByIdentity" interface which has been removed in v2::KeyChain.
07/19/2017
- 05:22 AM Task #2120 (Closed): Change the return type of InterestTable::erase(...) method to void
- 05:22 AM Bug #2996 (Closed): Build error in state.cpp
07/11/2017
- 11:13 AM Bug #4179: ChronoSync performs better without an exclude mechanism as publishing frequency increases
- After discussion on NFD call (07/10/17), Alex suggested that bug is that ChronoSync should not process exclude intere...
07/10/2017
- 01:52 PM Bug #4179: ChronoSync performs better without an exclude mechanism as publishing frequency increases
- With exclude: https://redmine.named-data.net/attachments/751/dfd.png
With no exclude: https://redmine.named-data.net... - 07:53 AM Bug #4179 (Closed): ChronoSync performs better without an exclude mechanism as publishing frequency increases
- With exclude mechanism, the performance seems worse with 5 nodes and an update rate of 13/second on average across th...
Also available in: Atom