6 packages tagged with “Comms”
A library based on the Reactive Extensions for simplifying device communications to embedded controllers, while guaranteeing correct sequencing and thread-safety of transactions. Originally developed for use with ASCOM device drivers, but may be useful for any software that needs to communicate with an embedded controller over a communications channel. The library offers classes that help with developing transactions, which model command/response protocols. The communications channel is abstracted into an interface, so that clients can easily switch between (say) serial or ethernet streams. Support for serial channels is built-in and custom channel implementations can easily be added and used. The client driver or application remains ignorant of the type of channel in use and just needs to save a "connection string" in settings to recreate the correct channel. For more information and a quick-start tutorial, please see http://tigra-astronomy.com/reactive-communications-for-ascom
GreenGo is a comms system used within the live events industry. This package allows you to load a GreenGo project, make changes and save the changes back to a project file that you can load into GreenGo Control software.
Extension for Alexa.NET library that adds Alexa.Comms.CallSignaling interface requests
TCP server and multi-client communications system.
A library based on the Reactive Extensions for simplifying device communications to embedded controllers, while guaranteeing correct sequencing and thread-safety of transactions (commands and responses). Originally developed for use with ASCOM device drivers, but useful for any software that needs to communicate with an embedded controller or attached device over a communications link. The library offers classes that help with developing transactions, which model command-response protocols. The communications channel is abstracted into an interface, so that clients can easily switch between (say) serial or ethernet streams. Support for serial channels is built-in and custom channel implementations can easily be added and used. The client driver or application remains ignorant of the type of channel in use and just needs to save a "connection string" in settings to recreate the correct channel.
A client used to interact with the restful Shuttle.Pigeon web API.