Footloose
Footloose is a fast and scalable asynchronous distributed computing and service library that was designed to be secure, simple to use, unobtrusive and without the need of client side code generation or proxy classes. It was developed to connect or build distributed applications on the .NET/Mono platform with enterprise features like load-balancing, clustering, encryption, service discovery and single-sign on. FEATURES - easy to use, only a few lines of code to start with Footloose - Publish-Subscribe - Unobtrusive, no Attributes like [OperationContract] and no base class required - No Code-Gen / Client Proxy Classes - keep your code clean - several TransportChannels: XMPP, IPC, AMQP - Security, Encryption and Compression (depends on Transport Channel) - Endpoint Capabilities and Service Discovery - Sharing Presence Information (Online, Offline, temp. unavailable, etc. incl. priority and reason) - Single-SignOn - bi-directional communication, no polling - Model driven - use your strongly-typed DTOs/POCOs LICENSE In order to use Footloose you need a valid license. You can request a free trial license at http://www.footloose-project.de/request-trial-license/ FURTHER INFORMATION The latest release and documentation can be found on the Footloose project website: http://www.footloose-project.de
Install
dotnet add package Footloose --version 3.0.0-beta1
Install-Package Footloose -Version 3.0.0-beta1
<PackageReference Include="Footloose" Version="3.0.0-beta1" />
Frameworks
No framework metadata available.
Dependencies
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
This version is marked prerelease. Validate its API and upgrade path before production use.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.