[Ndn-interest] Producer not receiving Interest, when starts a new thread.

[Anil Jangam]

Thanks Junxiao for the comments.

In my case, actually it is working. I have now moved the sendInterest();call
to onRegisterSuccess(const Name& prefix); method which is being called by
the setInterestFilter(). In my logic, I am receiving a return Interest from
remote end. Earlier, this was kicking in while register was in progress.
However, now with help of onRegisterSuccess(), I think there is one RTT
time available for registration of filter to go through.

I agree, in real world scenario, there will certainly be delay between when
producer initialize and when consumer starts requesting for data, and
therefore probability of this race condition, perhaps is lower, if not 0. I
was programatically forcing this race condition to occur and hence it
failed. I guess, for now I am good.

/anil.

On Wed, May 13, 2015 at 4:13 PM, Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Anil
>
> When onSuccess callback is invoked, it's not guaranteed for local NFD to
> deliver Interest toward the application.
> It only means the registration command has been accepted, but the command
> processing may still be in progress.
> See RIB Management protocol
> <http://redmine.named-data.net/projects/nfd/wiki/RibMgmt> "Semantics of
> successful responses" section for details. See also Bug 2761
> <http://redmine.named-data.net/issues/2761> for discussion on this
> behavior.
>
> The consumer is responsible for retransmissions until Interest is
> delivered to and answered by the producer.
>
> Yours, Junxiao
>
> On Wed, May 13, 2015 at 4:04 PM, Anil Jangam <anilj.mailing at gmail.com>
> wrote:
>
>> we need to wait till registration of the filter is successful. Let me
>> also implement the onSuccess() method, and then we won't have this
>> situation.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150513/a22f6309/attachment.html>