... respectively^3.1

This is mostly true, at least until the incoming and/or outgoing queues fill. If the incoming queue fills, then the client will be notified by the server (see Section 5.4). If the outgoing queue fills, then there is not really anthing to do; anyway this should not happen.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... interface^3.2

Conversely, a given driver may support multiple interfaces; the amcl and segwayrmp drivers demonstrate this idea.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... driver^3.3

This is almost true, except that the driver name is passed back to the client when a device is opened, just in case the client wants to do something driver-specific.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... (big-endian)^5.1

x86 machines are little-endian; thus clients running on them must byte-swap.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... number^5.2

This is the default port; Player can be configured to listen on a different port through a command-line option at startup. See Table 2.1.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... device^8.1

Most, but not all devices have their own threads.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... client^8.2

On Linux, due to the 10ms scheduler granularity, the effective upper limit on data rate is 50Hz.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.