Project

General

Profile

Actions

Task #1245

closed

Face list command

Added by Junxiao Shi over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Management
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
5.00 h

Description

Implement a handler for faces/list command, to publish the list of faces, and face counters.


Related issues 6 (0 open6 closed)

Related to NFD - Task #1328: nfd-status: plain text status commandClosedAlex Afanasyev

Actions
Blocked by NFD - Task #1280: Face counters skeletonClosedJunxiao Shi02/21/2014

Actions
Blocked by NFD - Task #1317: FaceTableClosedJunxiao Shi03/02/2014

Actions
Blocked by NFD - Task #1319: Face::getUriClosedAlex Afanasyev

Actions
Blocked by NFD - Task #1212: CS structureClosedIlya Moiseenko

Actions
Follows NFD - Task #1177: Face status protocolClosedJunxiao Shi

Actions
Actions #1

Updated by Junxiao Shi over 10 years ago

  • Assignee set to Anonymous

This task is ready to start.

Try to keep segmentation feature separate, so that it could be shared with #1192.

Actions #2

Updated by Anonymous over 10 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Anonymous over 10 years ago

How should the face list results be segmented into Data objects? My initial sketch was that I should try to put as many complete FaceStatus entries, up to some size limit, into a single Data.

However, after playing with this for a while, I'm getting errors attempting to decode the result with as few as 2 FaceStatus entries (just 1 works fine). I'm getting a "TLV length mismatches buffer length" exception when calling Block::blockFromValue on the Data's payload. I'm still unfamiliar with the library's encoding stuff, but is this because it's seeing the length of the first FaceStatus TLV and noticing it's smaller than the rest of the Data payload's buffer? (or Content TLV's length I guess?).

Actions #4

Updated by Junxiao Shi over 10 years ago

  1. collect all FaceStatus blocks into one chunk

  2. segment this chunk at arbitrary offsets (without considering FaceStatus block boundary, such that

    • Data packet does not exceed MAX_NDN_PACKET_SIZE after signing (it's better to be on the conservative side, such as having (MAX_NDN_PACKET_SIZE >> 1) octets of payload per packet
    • payloads in all Data packets, when combined sequentially, equals the chunk
  3. sequentially AppData.put those Data packets

    • segment 0 would satisfy the Interest
    • subsequent segments would go into the ContentStore

This task need not decode the Data packets. Decoding is in #1328.

Actions #5

Updated by Anonymous over 10 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 0 to 100
Actions #6

Updated by Anonymous over 10 years ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF