[Nfd-dev] client_server_communication

Ashlesh Gawande (agawande) agawande at memphis.edu
Mon Sep 11 08:34:01 PDT 2017


Does it work if you run everything on one node (or just outside of Mini-NDN)?

Seems like there are some errors in demo.html (Check console).

Also check the ping example:

https://github.com/named-data/ndn-js/tree/master/examples/ndnping


Ashlesh

________________________________
From: Nfd-dev <nfd-dev-bounces at lists.cs.ucla.edu> on behalf of Giuseppe Carella <gcarella228 at gmail.com>
Sent: Sunday, September 10, 2017 8:51:06 AM
To: nfd-dev at lists.cs.ucla.edu
Subject: [Nfd-dev] client_server_communication

Good morning,

I have a problem in the communication between an ndn-js client and ndn-cxx server.
I would like to establish a communication in localhost between client and server.
I run the server by means of mini-ndn:
a) I advertise the prefix on the server side using the command "producer nlsrc advertise /Demo/page"
b) I run the server in background on mini-ndn.
b) After that I run the client using mini-ndn using the command "client firefox demo.html"

The application is very easy: the client sends an interest packet and the server asnwers sending a data packet. The problem is that nothing works.

This is what I get on the command line:

mini-ndn> client firefox /home/giuseppe/Desktop/Demo/demo.html
1505051049132    addons.productaddons    WARN    Failed downloading XML, status: 0, reason: error
1505051049147    addons.productaddons    WARN    Failed downloading via XHR, status: 0, reason: error

My topology is the following one:

CLIENT-----GATEWAY----PRODUCER

I controlled the log file of client, gateway and producer.
The client and gateway only fill the FIB with the prefix I advertise on the server side (producer).

I attached both codes on client side and server side.


Thank you.
Best regards,
Giuseppe Carella.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170911/aefdb22d/attachment.html>


More information about the Nfd-dev mailing list