equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces
7.2.0
Prefix Reserved
See the version list below for details.
dotnet add package equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces --version 7.2.0
NuGet\Install-Package equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces -Version 7.2.0
<PackageReference Include="equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces" Version="7.2.0" />
paket add equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces --version 7.2.0
#r "nuget: equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces, 7.2.0"
// Install equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces as a Cake Addin #addin nuget:?package=equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces&version=7.2.0 // Install equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces as a Cake Tool #tool nuget:?package=equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces&version=7.2.0
equadrat Framework Net
The idea of the equadrat Framework is to provide APIs to build applications with an architecture of highly decoupled components. Every single component, aspect or pattern is represented by interfaces. The framework provides a standard implementation for these but each type can be replaced by a custom implementation.
The framework is not about reimplementing components, but making them available using common interfaces.
Status
Getting started
You can use most of the components by simply instantiating them. This is maybe the easiest way to evaluate the framework.
If you're using an IOC/DI container such as Microsoft Extensions DependencyInjection or if you want to use the built-in IOC framework, you can use the bootstrapper and bootstrapper modules to register the framework to the IOC.
Usage
- Get the INetTransportLayer of your choice from the INetTransportLayerProvider.
- Create and start a listener using the transport layer.
- Create and connect a client using the transport layer.
- Authentication (optional)
- Perform the authentication process of your coice on the client.
- Handle the authentication process accordingly on the server side.
- Protocol (optional)
- Create a raw/rpc connection on the client and server side.
- Declare the channels you want to use.
- Name
- Type: request (usually client side), response (usually server side), duplex
- Create a request/response channel to send/receive data.
- Each channel can have multiple request/response streams.
Have a look at the example applications on my website and in the wiki.
Interesting components
This is a list of some (not all) components of the framework which might be interesting for you.
Transport
- INetTransportLayerProvider
- INetTransportLayer
- NetTransportInMemoryLayer
- NetTransportTcpLayer
- NetTransportSecureLayer (SSL/TLS)
- INetTransportStreamWrapperFactory
- INetTransportPortManager
- X509Certificate2Builder (generate self-signed certificates, i.e. when running unit tests)
Authentication
- INetAuthenticationProcessProvider
- INetAuthenticationProcess
- NetAuthenticationNegotiateProcess (Windows NTLM/Kerberos)
- NetAuthenticationUserIdProcess (username + password)
- NetAuthenticationUserIdentityProcess (user id + signature, optional server password)
Protocol
- INetProtocolRawChannelConnectionFactory (each connection with multi byte-stream per channel)
- INetProtocolRpcChannelConnectionFactory (each connection with multi object-stream per channel)
Compatibility
The plan is to keep the equadrat Framework compatible to these .net versions as long as possible.
.net version | min | max |
---|---|---|
Core | 3.1 | ≥ 8.x |
Standard | 2.0 | ≥ 2.1 |
Framework | 4.6.2 | ≥ 4.8.x |
Version scheme and breaking changes
Version change | Scope |
---|---|
Major | Overhaul of the project |
Minor | Some types have changed |
Revision | Fully backward compatible |
Build | Set in preview versions only |
Additional documentation
You can find some guides regarding specific features on my website: www.equadrat.net
Feedback
You can contact me on my website: www.equadrat.net
License
Please respect the license and check equadrat.Framework.Net.License.md before using the package.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 is compatible. net5.0-windows was computed. net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 is compatible. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- equadrat.Framework.Core.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Protocol.Channel.Raw.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Transport.Interfaces (>= 7.2.0)
- Microsoft.Bcl.HashCode (>= 1.1.1)
-
.NETStandard 2.1
- equadrat.Framework.Core.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Protocol.Channel.Raw.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Transport.Interfaces (>= 7.2.0)
-
net5.0
- equadrat.Framework.Core.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Protocol.Channel.Raw.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Transport.Interfaces (>= 7.2.0)
-
net6.0
- equadrat.Framework.Core.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Protocol.Channel.Raw.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Transport.Interfaces (>= 7.2.0)
-
net7.0
- equadrat.Framework.Core.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Protocol.Channel.Raw.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Transport.Interfaces (>= 7.2.0)
-
net8.0
- equadrat.Framework.Core.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Protocol.Channel.Raw.Interfaces (>= 7.2.0)
- equadrat.Framework.Net.Transport.Interfaces (>= 7.2.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on equadrat.Framework.Net.Protocol.Channel.Rpc.Interfaces:
Package | Downloads |
---|---|
equadrat.Framework.Net.Protocol.Channel.Rpc
A framework to extend the Microsoft .net framework with extra net(work) functionality. |
GitHub repositories
This package is not used by any popular GitHub repositories.
====
v7.2.0
====
- Compatibility release
====
v7.1.0
====
- Initial development release