Add a wiki page describing the control protocol between the client and driver in a similar fashion to the network protocol specification.

This should include the requirements for memory ordering semantics and detection of dead publishers.

By publishing the protocol then the development of additional programming language clients

Please check the reproducible example here: https://github.com/michaelr524/reactor-netty-ssl-leak

mvn clean package
java -jar target/reactor-netty-ssl-leak-1.0-SNAPSHOT.jar 

• Reactor version(s) used: 0.9.4.RELEASE
• Other relevant libraries versions (eg. netty, ...):
• JVM version (javar -version):
  openjdk version "12.0.2" 2019-07-16
  OpenJDK Runtime Environment (build 12.0

I know you guys are focused on bringing more features to the lib, but it would be good to provide a bit better documentation and examples (I sent another post about this), so the ones willing to use the current version can fully understand what they can do with it..

E.g.

• I am not sure how to use signals, I can see raft::fileread uses raft::eof, but not sure what is done with it.
• I don't

Describe the bug
The device controlboard has been deprecated in favor of controlboardwrapper2. Therefore, the documentation available at http://www.yarp.it/yarp_without_yarp.html that relies on controlboard for the test scenario needs to be updated accordingly.

To Reproduce
Launch:

$ yarpdev --device controlboard --subdevice test_motor --name /motor --axes 5

**Sc

Should "...is available which allows interaction with C++ as well." be instead "is available which allows interaction with C# as well."?

Besides the lack of decent documentation, we also have another major doc-related issue: some of the docs and examples that we do have are vastly outdated and misleading. These must be fixed to reflect the current state of the project.

Ref: metarhia/jstp#151