- 23 Oct, 2015 40 commits
-
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
* No component external to namespace needs to know.
-
Thomas Jahns authored
* PIO client can only ever be invoked on active namespaces, other stages no longer exist.
-
Thomas Jahns authored
-
Thomas Jahns authored
* Namespaces are either in-use or unused, no further state logic is required.
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
* Having a configuration object will allow future extensions without a change of interface to cdiPioInit. * Also move code to translate I/O mode string vs. integer into library.
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
-
Thomas Jahns authored
* The function is correspondingly renamed to reflect the narrower functionality.
-
Thomas Jahns authored
* Now that setting up of communications has been consolidated in cdiPioCommInit, the initial callback of cdiPioInit can now be called regardless of backend mode.
-
Thomas Jahns authored
* Every server now serves a subset of the clients only.
-