Rask.Signaling 0.21.0

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer prerelease version of this package available.
See the version list below for details. 
dotnet add package Rask.Signaling --version 0.21.0
                    


                    

                
NuGet\Install-Package Rask.Signaling -Version 0.21.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Rask.Signaling" Version="0.21.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Rask.Signaling" Version="0.21.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Rask.Signaling" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Rask.Signaling --version 0.21.0
                    


                    

                
#r "nuget: Rask.Signaling, 0.21.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package Rask.Signaling@0.21.0
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Rask.Signaling&version=0.21.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Rask.Signaling&version=0.21.0
                    


                            Install as a Cake Tool

Rask.Signaling

The WebRTC signaling relay that Rask's ISignaling client connects to — the channel two peers trade an offer, an answer and their ICE candidates over before they can reach each other directly.

It depends on nothing from Rask.Server, only ASP.NET routing and WebSockets, so any ASP.NET host can map it — including a static-file host serving a published WASM bundle.

builder.Services.AddRaskSignaling(o =>
{
    // The framework can't know who belongs in which room. This is where you say.
    o.AuthorizeRoom = ctx => ctx.Services
        .GetRequiredService<IConversations>()
        .IsMemberAsync(ctx.User, ctx.Room);
});

app.MapRaskSignaling();

The host must have WebSocket support in the pipeline: Rask.Server's UseRask() calls app.UseWebSockets() for you, but a static-file host serving a published WASM bundle does not — call it yourself before mapping. The relay says so explicitly rather than refusing clients with a bare 400.

What it guarantees

It is a relay between untrusted peers, so:

  • Peer ids are minted by the server, never taken from the client.
  • A message reaches only a peer in the sender's own room, checked at delivery.
  • Nothing is ever echoed back to its sender.
  • Payload size, message rate, room size and room count are capped.
  • Authentication is required by default — a relay anyone can join is a way to reach other people's browsers, so opening it should be a decision, not an accident.
  • A refused join says the same thing whether the room was full or you weren't allowed in, so a caller can't probe which rooms exist.

The payload is an opaque string. The relay never parses an SDP or an ICE candidate — only the two browsers need to understand it.

Limits

Rooms are held in memory, per process. Signaling is short-lived, so there is nothing worth persisting, but a multi-instance deployment needs sticky routing on the signaling path — two peers assigned to different instances never see each other.

See also

  • docs/apis/signaling.md — the client half (ISignaling, in Rask.Core)
  • docs/apis/webrtc.md — what the signaling is for
Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

  • net10.0

    • No dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.21.1-alpha.0.49 41 9/12/2026
0.21.1-alpha.0.47 27 9/12/2026
0.21.1-alpha.0.45 29 9/12/2026
0.21.1-alpha.0.44 26 9/12/2026
0.21.1-alpha.0.43 28 9/12/2026
0.21.1-alpha.0.40 29 9/12/2026
0.21.1-alpha.0.39 35 9/11/2026
0.21.1-alpha.0.38 34 9/11/2026
0.21.1-alpha.0.37 28 9/11/2026
0.21.1-alpha.0.36 39 9/11/2026
0.21.1-alpha.0.35 34 9/11/2026
0.21.1-alpha.0.34 36 9/11/2026
0.21.1-alpha.0.33 34 9/11/2026
0.21.1-alpha.0.32 37 9/11/2026
0.21.1-alpha.0.31 33 9/11/2026
0.21.1-alpha.0.30 36 9/11/2026
0.21.1-alpha.0.29 33 9/11/2026
0.21.1-alpha.0.27 32 9/11/2026
0.21.1-alpha.0.25 30 9/11/2026
0.21.0 40 9/10/2026
Loading failed