Wiki » History » Revision 21
Revision 20 (Alex Afanasyev, 07/21/2014 01:21 PM) → Revision 21/27 (Alex Afanasyev, 07/23/2014 04:46 PM)
Repo protocol and repo-ng ============= ## Repo protocol **Repo protocol** is semantics and operating process for persistent storage node in NDN. The operation of NDN repo includes reading from, insertion to and deleting from data objects in NDN repository nodes. **Repo protocol** is based on [Command Interests](http://redmine.named-data.net/projects/nfd/wiki/Command_Interests) specification. **Repo protocol** conforms to [[Repo Protocol Specification|Repo Protocol Specification]] **protocols and specifications** for operating and controlling, including a set of repo management protocols: controlling. - **[[Repo Command]]** defines the request and response formats * [NFD command interests](http://redmine.named-data.net/projects/nfd/wiki/Command_Interests) for constructing signed interest of commands that can insert or remove data from repo, and how these commands should be signed and authenticated. access control. - **[[Basic Repo Insertion Protocol]]** defines format * [[Repo Protocol Specification|Repo Protocol Specification]] * [NFD Control Command specification](http://redmine.named-data.net/projects/nfd/wiki/ControlCommand): The reponse of insertion of a single or collection of Data packets. In addition to and deletion command will follow the basic protocol, repo-ng implements several other insertion protocols: + **[[Watched Prefix Insertion Protocol]]** defines a protocol to insert continuously generated data + **[[Tcp Bulk Insert Repo Insertion Protocol]]** defines a simple TCP-based protocol to insert Data packets in bulk (e.g., from a producer on the same host) - **[[Repo Deletion Protocol]]** defines response format of deletion this specification, but with different defination of a single or collection of Data packets under certain prefix status code. ## repo-ng **repo-ng** (repo-new generation) is an implementation of NDN persistent in-network storage conforming to **Repo protocol**. It uses [ndn-xx](http://redmine.named-data.net/projects/ndn-cxx) as NDN client library and database sqlite3 as underlying data storage. ### platform and libraries * [C++ 03](http://en.cppreference.com/w/), [code style guidelines](http://redmine.named-data.net/projects/nfd/wiki/CodeStyle) * [Boost >=1.48.0](http://www.boost.org/doc/libs/1_48_0/), we use [|a limited set of Boost libraries](http://redmine.named-data.net/projects/nfd/wiki/Boost) * [Boost Unit Test Framework](http://www.boost.org/doc/libs/1_48_0/libs/test/doc/html/index.html), more information on [[unit testing](http://redmine.named-data.net/projects/nfd/wiki/UnitTesting) * [ndn-cxx](https://github.com/named-data/ndn-cxx), Extended version of NDN C++ client library * [waf build system](https://code.google.com/p/waf/) * [sqlite3](http://sqlite.org/) ### specific design * [[Database design|Database design]] * [[Software Structure|Software Structure]] ### current supported functions Most parts of the protocol are supported in repo-ng. The following specifications are not supported in current version. * For deletion command, if EndBlockId is null in RepoCommandParameter, repo cannot response all the segmented data from StartBlockId * Command for checking deletion progress Trust model of command validation and access control have not been designed. All the commands are validated in current version and all the commands could pass.