Notification » History » Version 2
Junxiao Shi, 02/10/2014 08:58 PM
1 | 1 | Junxiao Shi | # NFD Notification mechanism |
---|---|---|---|
2 | |||
3 | NFD Notification mechanism notifies applications about events happening inside NFD. |
||
4 | |||
5 | ## Naming |
||
6 | |||
7 | * A stream of notifications is published under a certain Name prefix. |
||
8 | 2 | Junxiao Shi | * A notification is a Data packet under this Name prefix with a sequence number. |
9 | * The sequence numbers of notifications in the same stream should be consecutive and increasing. |
||
10 | * Each notification is limited to one Data packet. |
||
11 | 1 | Junxiao Shi | |
12 | Example: |
||
13 | |||
14 | 2 | Junxiao Shi | ndn:/localhost/nfd/faces/events/%01 // first notification |
15 | ndn:/localhost/nfd/faces/events/%02 // second notification |
||
16 | 1 | Junxiao Shi | |
17 | ## Notification publisher |
||
18 | |||
19 | Notifications from NFD are Data packets generated and signed by NFD. |
||
20 | |||
21 | These Data packets enter forwarding system via the InternalFace, and are subject to regular forwarding pipelines. |
||
22 | They should be admitted into the ContentStore. |
||
23 | |||
24 | ## Notification subscriber |
||
25 | |||
26 | 2 | Junxiao Shi | The subscriber should typically request the Name of notification stream (`ndn:/localhost/nfd/faces/events` in the example) with ChildSelector=1 and Exclude=\<Any>\<Component>*seq*\</Component>, where *seq* is the version number of the latest received notification. |
27 | 1 | Junxiao Shi | |
28 | 2 | Junxiao Shi | * If no new notification has been generated after *seq*, this Interest will stay in the PIT, and be satisfied when a new notification is generated. |
29 | * If one or more new notifications have been generated after *seq*, the Interest will be satisfied from the ContentStore, and the latest notification is returned. |
||
30 | The subscriber can retrieve missing notifications between *seq* and the returned latest notification by expressing additional Interests. |