NDN-CCL

07/07/2017

09:27 PM Bug #4160 (Rejected): the default time uint is millisecond while ndn-cxx uses nanosecond

This is not a bug, it is an API design decision. The API calls perform as documented and encode/decode the correct co... Jeff Burke

07/06/2017

11:04 PM Bug #4160: the default time uint is millisecond while ndn-cxx uses nanosecond

I need to correct myself first: ndn-cxx uses "microseconds", which is consistent with the Name Conventions document; ... Haitao Zhang

12:21 AM Bug #4160: the default time uint is millisecond while ndn-cxx uses nanosecond

Actually, the jNDN fromTimestamp and toTimestamp just encode and decode the number that it is given, without converti... Anonymous

07/05/2017

10:58 PM Bug #4160: the default time uint is millisecond while ndn-cxx uses nanosecond

For example, a timestamp component is created using jNDN's Component.fromTimestamp(); when it is converted back to ti... Haitao Zhang

11:28 AM Bug #4160: the default time uint is millisecond while ndn-cxx uses nanosecond

The CCL is not meant to have the exact API as ndn-cxx. Can you give an example of communication problems? Anonymous

10:56 AM Bug #4160 (Rejected): the default time uint is millisecond while ndn-cxx uses nanosecond

This causes problems when programs based on ndn-ccl libraries need to communicate with problems based on ndn-cxx Haitao Zhang