| commit | 0b688dca539c1c56707bbb1c31a92a6d6ffd025f | [log] [tgz] |
|---|---|---|
| author | Alexander Afanasyev <alexander.afanasyev@ucla.edu> | Wed Dec 18 16:43:37 2013 -0800 |
| committer | Alexander Afanasyev <alexander.afanasyev@ucla.edu> | Thu Jan 09 15:13:44 2014 -0800 |
| tree | ed8087c1e027f543c895e5310732cdba4a838552 | |
| parent | 0c6321101ba893370873380d3c28fdf01f368954 [diff] |
face+transport: Eliminating concept of ConnectionInfo The current "transport" is not really a transport, rather than a connection, which completely handles all connection-specific tasks. I don't see any reason for not to keep connection information as inherent property of the "transport". Change-Id: Ib06697522d1b8f5b22d82fa86994056a9b0b7dec
NDN-CPP is a new implementation of a Named Data Networking client library written in C++ and C.
It is wire format compatible with NDNx and PARC's CCNx.
NDN-CPP is open source under a license described in the file COPYING. While the license does not require it, we really would appreciate it if others would share their contributions to the library if they are willing to do so under the same license.
See the file INSTALL for build and install instructions.
Please submit any bugs or issues to the NDN-CPP issue tracker: http://redmine.named-data.net/projects/ndn-cpp/issues
The library currently requires a remote NDN daemon, and has been tested with ndnd, from the NDNx package: https://github.com/named-data/ndnx .
Currently, the library has two APIs for developers:
1. The C++ API which follows the NDN Common Client Library API also used by ndn-js (JavaScript) and PyNDN (Python). 2. A core C library implementing lower-level encoding and communication. Applications should normally use the C++ API, but core C code will also function on embedded devices and other environments which don't have C++ support.