Team2890/allwpilib
4
0
Fork 0
mirror of https://github.com/wpilibsuite/allwpilib synced 2026-06-19 00:41:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

[ntcore] Use "NetworkTables" instead of "Network Tables" in NT specs (#3477)

Browse Source 
Closes #3280.
This commit is contained in:
Tyler Veness
2021-07-11 10:37:27 -04:00
committed by GitHub
parent 5f5830b960
commit 1adb69c0fd
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
ntcore/doc/networktables2.adoc
View File

@@ -1,4 +1,4 @@
= Network Tables Protocol Specification, Version 2.0
= NetworkTables Protocol Specification, Version 2.0
WPILib Developers <wpilib@wpi.edu>
Protocol Revision 2.0 (0x0200), 1/8/2013
:toc:
@@ -19,9 +19,9 @@ updates which have a larger sequence number than its own, which guarantees that
a client must have received a server's most recent state before it can replace
it with a new value.
This is a backwards-incompatible rework of the Network Tables network protocol
This is a backwards-incompatible rework of the NetworkTables network protocol
originally introduced for the 2012 FIRST Robotics Competition. Note that this
revision of the Network Tables protocol no longer includes the concept of
revision of the NetworkTables protocol no longer includes the concept of
sub-tables. We suggest that instead of representing sub-tables as first-class
data types in the network protocol, it would be easy for an implementation to
provide a similar API abstraction by adding prefixes to keys. For example, we

8
ntcore/doc/networktables3.adoc
View File

@@ -1,4 +1,4 @@
= Network Tables Protocol Specification, Version 3.0
= NetworkTables Protocol Specification, Version 3.0
WPILib Developers <wpilib@wpi.edu>
Protocol Revision 3.0 (0x0300), 6/12/2015
:toc:
@@ -20,7 +20,7 @@ a client must have received a server's most recent state before it can replace
it with a new value.
This is a backwards-compatible update of <<networktables2,version 2.0>> of the
Network Tables network protocol. The protocol is designed such that 3.0 clients
NetworkTables network protocol. The protocol is designed such that 3.0 clients
and servers can interoperate with 2.0 clients and servers with the only loss of
functionality being the extended features introduced in 3.0.
@@ -50,7 +50,7 @@ the deletion message will not be propagated to the 2.0 Clients.
Remote procedure call:: The Server may create specially-typed entries that
inform Clients of remotely callable functions on the Server. Clients can then
execute these functions via the Network Tables protocol. See <<rpc-operation>>.
execute these functions via the NetworkTables protocol. See <<rpc-operation>>.
Raw data type:: An arbitrary data type has been added. While string could be
used to encode raw data, the reason for a different data type is so that
@@ -108,7 +108,7 @@ conflicting values when reconnecting to a Server has been clarified.
== References
[[networktables2]]
* <<networktables2.adoc#,Network Tables Protocol Specification, Protocol
* <<networktables2.adoc#,NetworkTables Protocol Specification, Protocol
Revision 2.0 (0x0200)>>, dated 1/8/2013.
[[leb128,LEB128]]