Resonance.USB 1.0.0-beta

USB Adapter for Resonance.

Resonance is a high-performance real-time C# communication library with built-in support for several different transcoding and delivery methods. This library provides an intuitive API for asynchronous communication between machines and devices by exposing a set of easy to use, pluggable components.

This is a prerelease version of Resonance.USB.
There is a newer version of this package available.
See the version list below for details.
Install-Package Resonance.USB -Version 1.0.0-beta
dotnet add package Resonance.USB --version 1.0.0-beta
<PackageReference Include="Resonance.USB" Version="1.0.0-beta" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Resonance.USB --version 1.0.0-beta
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: Resonance.USB, 1.0.0-beta"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install Resonance.USB as a Cake Addin
#addin nuget:?package=Resonance.USB&version=1.0.0-beta&prerelease

// Install Resonance.USB as a Cake Tool
#tool nuget:?package=Resonance.USB&version=1.0.0-beta&prerelease
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

Resonance

Resonance is a high-performance real-time C# communication library with built-in support for several different transcoding and delivery methods. This library provides an intuitive API for asynchronous communication between machines and devices by exposing a set of easy to use, pluggable components.

Overview

Resonance is a request-response based communication framework. This means that for each request that is being sent, a matching response is expected. This is done by attaching a unique token to each request and expecting the same token from the response. Although the request-response pattern is the recommended approach, it is not enforced. Sending messages without expecting any response is possible.

The resonance library might be described by these 3 basic layers:

Transporting

A transporter responsibility is to provide the API for sending and receiving messages, managing those messages, and propagating the necessary information to other components.

Transcoding

Encoders and Decoders are components that can be plugged to a transporter, they determine how outgoing/incoming messages should be encoded and whether the data should be encrypted and/or compressed. The Following built-in transcoding methods are currently supported by the library:

  • Json
  • Bson
  • Protobuf
  • Xml

Adapters

Adapters can also be plugged to a transporter to determine how outgoing/incoming encoded data is going to be transmitted and where. The following built-in adapters are currently supported by the library:

  • TCP
  • UDP
  • USB
  • In-Memory
  • SignalR
  • WebRTC
  • Named Pipes
  • Shared Memory

Resonance

Resonance is a high-performance real-time C# communication library with built-in support for several different transcoding and delivery methods. This library provides an intuitive API for asynchronous communication between machines and devices by exposing a set of easy to use, pluggable components.

Overview

Resonance is a request-response based communication framework. This means that for each request that is being sent, a matching response is expected. This is done by attaching a unique token to each request and expecting the same token from the response. Although the request-response pattern is the recommended approach, it is not enforced. Sending messages without expecting any response is possible.

The resonance library might be described by these 3 basic layers:

Transporting

A transporter responsibility is to provide the API for sending and receiving messages, managing those messages, and propagating the necessary information to other components.

Transcoding

Encoders and Decoders are components that can be plugged to a transporter, they determine how outgoing/incoming messages should be encoded and whether the data should be encrypted and/or compressed. The Following built-in transcoding methods are currently supported by the library:

  • Json
  • Bson
  • Protobuf
  • Xml

Adapters

Adapters can also be plugged to a transporter to determine how outgoing/incoming encoded data is going to be transmitted and where. The following built-in adapters are currently supported by the library:

  • TCP
  • UDP
  • USB
  • In-Memory
  • SignalR
  • WebRTC
  • Named Pipes
  • Shared Memory

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version History

Version Downloads Last updated
1.8.0 108 6/25/2021
1.7.2-pre 105 6/25/2021
1.7.1-pre 112 6/24/2021
1.7.0 64 5/27/2021
1.6.1-pre 154 5/22/2021
1.6.0 85 5/20/2021
1.5.3-pre 96 5/19/2021
1.5.2-pre 59 5/19/2021
1.5.1-pre 46 5/18/2021
1.5.0 95 5/6/2021
1.4.0 53 5/4/2021
1.3.2-pre 117 5/2/2021
1.3.0 59 4/30/2021
1.2.14-pre 60 4/30/2021
1.2.13-pre 59 4/30/2021
1.2.12-pre 63 4/30/2021
1.2.9-pre 72 4/30/2021
1.2.8-pre 79 4/27/2021
1.2.7-pre 49 4/27/2021
1.2.6-pre 45 4/27/2021
1.2.5-pre 55 4/27/2021
1.2.0 78 4/24/2021
1.1.2-pre 79 4/24/2021
1.1.1-pre 90 4/24/2021
1.1.0 73 4/24/2021
1.0.12-pre 78 4/24/2021
1.0.11-pre 86 4/24/2021
1.0.0-beta 66 4/22/2021
Show less