Changes between Version 40 and Version 41 of GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Execute

Timestamp:

07/05/16 11:28:08 (8 years ago)

Author:

tteixeir@bbn.com

Comment:

--

GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Execute

@@ -75 +75 @@
 SSH to the {{{Experimenter}}} node, and start the consumer application
      {{{
-     $ time sudo python /local/consumer.py -u /nytimes/science
+     $ sudo python /local/consumer.py -u /nytimes/science
      }}}
 The {{{Interest}}} packet travels the entire topology, leaving breadcrumbs. The {{{Data}}} packet follows the breadcrumbs back to the {{{consumer}}}, leaving cached versions of the content. This is call in-network caching and it is one of the most important features in {{{Information Centric Networking (ICN)}}}
@@ -81 +81 @@
 SSH to the {{{PI}}} node and start the consumer application
      {{{
-     $ time sudo python /local/consumer.py -u /nytimes/science
+     $ sudo python /local/consumer.py -u /nytimes/science
      }}}
 This time your {{{PI}}} node gets the content back, but nothing happens on the {{{Custodian}}} because the requested content is cached in the {{{Campus Router}}} node.[[br]]
-Note that this time the {{{Data}}} was retrieved much faster.[[br]]
+Note that the {{{Data}}} was retrieved much faster.[[br]]
 You can repeat the experiment with different namespaces
      {{{ 
-     $ time sudo python /local/consumer.py -u /nytimes/math
+     $ sudo python /local/consumer.py -u /nytimes/math
      }}}
 This time you see that the {{{Interest}}} request is served by the {{{Custodian}}}.
+[[br]]
+Feel free to explore different {{{namespaces}}}.
 
 === 5.2 (Optional) Visualize experiment data flows ===