From 1f28ce398078eff39081ef25e7c1e234dd6f8fc2 Mon Sep 17 00:00:00 2001 From: Adam Ierymenko Date: Wed, 1 Apr 2015 19:09:18 -0700 Subject: Tons more refactoring: simplify Network, move explicit management of Tap out, redo COM serialization, etc. --- node/Packet.hpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'node/Packet.hpp') diff --git a/node/Packet.hpp b/node/Packet.hpp index 75e595fc..78231aac 100644 --- a/node/Packet.hpp +++ b/node/Packet.hpp @@ -596,10 +596,10 @@ public: * <[8] 64-bit network ID> * <[2] 16-bit length of request meta-data dictionary> * <[...] string-serialized request meta-data> - * [<[8] 64-bit timestamp of netconf we currently have>] + * [<[8] 64-bit revision of netconf we currently have>] * * This message requests network configuration from a node capable of - * providing it. If the optional timestamp is included, a response is + * providing it. If the optional revision is included, a response is * only generated if there is a newer network configuration available. * * OK response payload: @@ -614,7 +614,7 @@ public: * a given network. * * When a new network configuration is received, another config request - * should be sent with the new netconf's timestamp. This confirms receipt + * should be sent with the new netconf's revision. This confirms receipt * and also causes any subsequent changes to rapidly propagate as this * cycle will repeat until there are no changes. This is optional but * recommended behavior. -- cgit v1.2.3