[Ndn-interest] Bind Application with NDN layer

Nick Briggs nicholas.h.briggs at gmail.com
Thu Apr 20 08:20:06 PDT 2017

The logical equivalent to TCP/IP's bind is when the application registers with the NDN/CCN daemon indicating that it will handle Interests in a particular prefix of the namespace.  The TCP/IP socket number is logically a 16-bit extension of the IP address namespace -- in NDN/CCN the namespace is much larger and is not divided into host IP/port.

-- Nick Briggs
> On Apr 20, 2017, at 2:10 AM, n.boubakr at bit.edu.cn wrote:
> Hello,
> Talking about the Application layer in both TCP/IP and NDN stacks. In TCP/IP, I have to bind each application with Port number using socket concept, to allow the application to answer to different requests. In NDN environment, there is no concept of sessions, sockets… How can we bind our applications with NDN.
> Let’s take an example of Web Server, in traditional network HTTP/S works on port 80, and it responses to different requests by targeting the client port number.
> In NDN, if I want to implement such as Web Server, how to bind it with NDN layer, it will response to all Interest with the same manner? What if the content is dynamic? Does intermediate router will cache that dynamic content? Or it’s possible only for static content?
> Boubakr Nour (Ph.D Student)
> Beijing Institute of Technology (北京理工大学)
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest <http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170420/db558cb7/attachment-0001.html>

More information about the Ndn-interest mailing list