jndn

03/26/2015

10:42 AM Bug #1518 (Abandoned): registerPrefix adds the onInterest callback even when registration fails

This is the same as bug #1517 in the Redmine for all libraries, so abandon this one. Anonymous

03/09/2015

03:11 PM Bug #2560 (Closed): mvn integration-test doesn't seem to run the tests

Great, thanks. I merged to master and will make a Maven release. Anonymous

12:18 PM Bug #2560: mvn integration-test doesn't seem to run the tests

Jeff, I believe that was an auto-refactor artifact and not intentional; I removed them in the latest commit. Andrew Brown

11:43 AM Bug #2560 (In Progress): mvn integration-test doesn't seem to run the tests

Hi Andrew. Sounds good and thanks for using the convention for the branch name. It works for me after updating a few ... Anonymous

10:21 AM Bug #2560: mvn integration-test doesn't seem to run the tests

Jeff, check out the branch I published. I had to move the integration-tests back under the global tests folder for fa... Andrew Brown

03/06/2015

02:39 PM Feature #2565: Implement async operations for Face.processEvents

On my list it is near the top. Infinite loops with poll and sleep operations, specifically in android case would unn... Alex Afanasyev

03/05/2015

11:56 AM Task #2619 (Closed): Data.setName, etc. do not copy the object

Anonymous

10:59 AM Task #2619 (Closed): Data.setName, etc. do not copy the object

The API doc for Data.setName, etc. say that the method copies the object: http://named-data.net/doc/ndn-ccl-api/data.... Anonymous

03/04/2015

11:04 PM Feature #2565: Implement async operations for Face.processEvents

+1. Any thoughts on priority relative to other issues? Jeff Burke

10:33 PM Feature #2578: Callback classes should not be under net.named_data.jndn, but at some higher level

Makes sense to consider this. How much of a priority do you think it is? Jeff Burke

02/27/2015

03:59 PM Task #2545 (Closed): Blob should support hashCode()

The change for Blob.hashCode to use ByteBuffer.hashCode is merged into the master branch. Anonymous

02/26/2015

10:51 AM Task #2545: Blob should support hashCode()

No worries, I understand the concerns. Andrew Brown

10:50 AM Task #2545: Blob should support hashCode()

Oh. ok, I'm got mislead by the question and like this approach. Please ignore my notes 28, 29. Alex Afanasyev

10:45 AM Task #2545: Blob should support hashCode()

Look down to the answer to that question: the OP was not filling the buffer, therefore the hash was always the same. Andrew Brown

10:36 AM Task #2545: Blob should support hashCode()

Andrew Brown wrote:
> I don't understand: in #28 you say ByteBuffer.hashCode() is not a real hash but it actually ... Alex Afanasyev

10:30 AM Task #2545: Blob should support hashCode()

I don't understand: in #28 you say ByteBuffer.hashCode() is not a real hash but it actually is (see #25, just not a c... Andrew Brown

10:04 AM Task #2545: Blob should support hashCode()

Just forgot to add that we would still need to implement real (as it note-25) hashCode() for name and name components... Alex Afanasyev

09:53 AM Task #2545: Blob should support hashCode()

ByteBuffer.hashCode() doesn't do any real hashing (value depends on the number of remaining bytes). I don't mind usi... Alex Afanasyev

09:23 AM Task #2545: Blob should support hashCode()

Nice, I like it. Alex? Andrew Brown

09:04 AM Task #2545: Blob should support hashCode()

The ByteBuffer position and limit will not change, nor will its contents. I hadn't noticed that ByteBuffer implement... Anonymous

08:49 AM Task #2545: Blob should support hashCode()

I understand and that makes sense, just note from previous comments that I was advocating using the same hash as Stri... Andrew Brown