diff options
| author | Kees Bos <k.bos@capitar.com> | 2015-05-06 12:05:20 +0200 |
|---|---|---|
| committer | Kees Bos <k.bos@capitar.com> | 2015-05-06 12:05:20 +0200 |
| commit | a425bbc67301bf486fe5b0aba8adb59ae791403e (patch) | |
| tree | 460b6c5a5c2ed852903fac2a9703c6f06534f79f /service | |
| parent | 845955dea53035e8472059ff03feca9f47c0d5fa (diff) | |
| download | infinitytier-a425bbc67301bf486fe5b0aba8adb59ae791403e.tar.gz infinitytier-a425bbc67301bf486fe5b0aba8adb59ae791403e.zip | |
Renamed supernode to rootserver
Diffstat (limited to 'service')
| -rw-r--r-- | service/ControlPlane.cpp | 2 | ||||
| -rw-r--r-- | service/README.md | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/service/ControlPlane.cpp b/service/ControlPlane.cpp index 4158ed43..e42c9ef8 100644 --- a/service/ControlPlane.cpp +++ b/service/ControlPlane.cpp @@ -213,7 +213,7 @@ static void _jsonAppend(unsigned int depth,std::string &buf,const ZT1_Peer *peer switch(peer->role) { case ZT1_PEER_ROLE_LEAF: prole = "LEAF"; break; case ZT1_PEER_ROLE_HUB: prole = "HUB"; break; - case ZT1_PEER_ROLE_SUPERNODE: prole = "SUPERNODE"; break; + case ZT1_PEER_ROLE_ROOTSERVER: prole = "ROOT"; break; } Utils::snprintf(json,sizeof(json), diff --git a/service/README.md b/service/README.md index 2a283cbd..df62ff27 100644 --- a/service/README.md +++ b/service/README.md @@ -106,7 +106,7 @@ Getting /peer returns an array of peer objects for all current peers. See below <tr><td>versionRev</td><td>integer</td><td>Revision of remote if known</td><td>no</td></tr> <tr><td>version</td><td>string</td><td>Version in major.minor.rev format</td><td>no</td></tr> <tr><td>latency</td><td>integer</td><td>Latency in milliseconds if known</td><td>no</td></tr> -<tr><td>role</td><td>string</td><td>LEAF, HUB, or SUPERNODE</td><td>no</td></tr> +<tr><td>role</td><td>string</td><td>LEAF, HUB, or ROOTSERVER</td><td>no</td></tr> <tr><td>paths</td><td>[object]</td><td>Array of path objects (see below)</td><td>no</td></tr> </table> @@ -184,7 +184,7 @@ Relays, IP assignment pools, and rules are edited via direct POSTs to the networ **Relay object format:** -Relay objects define network-specific preferred relay nodes. Traffic to peers on this network will preferentially use these relays if they are available, and otherwise will fall back to the global supernode infrastructure. +Relay objects define network-specific preferred relay nodes. Traffic to peers on this network will preferentially use these relays if they are available, and otherwise will fall back to the global rootserver infrastructure. <table> <tr><td><b>Field</b></td><td><b>Type</b></td><td><b>Description</b></td></tr> |