Repo Serves Clients + Client App Redone

[justincpresley]

This Pull accomplishes two tasks:

• sort out how a repo node replies to interests
• redo the client application

This Pull DOES NOT accomplish client file fetching. This is in the process of being done, and only sets up how the repo will respond.

New Client Functionality:

All functions (dump, insert, delete, fetch) are done by doing:

• python3 main.py fetch
• python3 main.py delete
• python3 main.py dump
• python3 main.py insert

Some of these (in fact all of them) have their own arguments (indicated by a -letter) that you need to fulfill for example:

• python3 main.py insert -f "/file1" -p "./examples/t.txt"

If you run the client application, it will tell you this entire process. The application will correct you.

New Repo Functionality:

The repo will respond with either a NACK, BLOB, or LINK data packet. The first two self-explanatory, the latter being the correct prefix to go to (does not include segmenting). For example if the client wants /drepo/main/file1/seg=0, then the link will provide /drepo/id/node5/file1 for example. The Client is responsible getting what packets it needs.

While the Repo can not be tested yet. The New Client should be tested before pushing it to main.

[ZixuanZhong]

you should use global_view_2 instead of global_view everywhere. Plz change that in ndn_distributed_repo/handle_protocol/read_handle.py, thx!

[justincpresley]

I sorted out the database problems. No problems on my end with merging now.