Activity
From 04/10/2018 to 05/09/2018
05/08/2018
-
09:02 AM Task #4606: TestChronoSync: All users not receiving chat messages
- Ah, that makes perfect sense. Thank you so much for the update.
-
08:47 AM
Task #4606: TestChronoSync: All users not receiving chat messages
- The original design for conflict recover (not in ChronoSync2013) requires the Interest Exclude filter, which is being...
05/07/2018
-
- I updated my code base to simulate a chat more in the spirit of what you suggested around allowing ChronoSync to "rea...
05/03/2018
-
- Of course!
Currently the chat delay is
```
@Override
public long getChatDelayTime() {
int range = 1000;
... -
12:51 PM
Task #4606: TestChronoSync: All users not receiving chat messages
- Hi Price. If multiple users issue new chat messages in less time than the ChronoSync system can reach a new concensus...
-
12:45 PM
Task #4606 (Closed): TestChronoSync: All users not receiving chat messages
- From Price Clarke:
I started testing Chronosync by getting started with the TestChronoSync demo code and kept runn...
04/11/2018
-
08:25 AM
Bug #4575 (Closed): fail to register prefix with NFD-android using NDN-DOT-NET library
- Great. Closing.
04/10/2018
-
11:48 PM Bug #4575: fail to register prefix with NFD-android using NDN-DOT-NET library
- it works now, thanks
-
- sure, thanks
-
02:03 PM
Bug #4575 (Feedback): fail to register prefix with NFD-android using NDN-DOT-NET library
- I pushed a fix to implement isLocal() using the .NET IsLoopback.<br>
https://github.com/named-data/ndn-dot-net/blob/... -
- I would say yes.
Since the registration succeeded on the remote NFD, I think the command itself is ok. It fails wit... -
01:29 PM
Bug #4575: fail to register prefix with NFD-android using NDN-DOT-NET library
- Do you think it would work if it used /localhost ?
-
- we were trying to register a prefix from the APP (built on top of NDN-NOT-NET) to NFD-Android, but it failed.
But it...
Also available in: Atom