aws / aws/aws-lambda-dotnet

Allow DotNet SignalR to work with AWS WebSockets API

Open
#913 6 comments 0 reactions 0 assignees View on GitHub
feature-request module/aspnetcore-support p3
Dominant language
C#
Stars
1.7k
Forks
503
Avg merge
1d 5h
Merged PRs (30d)
18

Description

My goal is to allow DotNet SignalR client and server to communicate via the AWS WebSockets API.

This would allow us to use Blazor server-side components in an AWS Lambda DotNet application.

After looking at this for some time I believe that we need a new HttpTransportType which is part LongPolling (for the incoming HTTPRequest to Lambda from AWS WebSockets API) and part WebSockets (for the immediate response back to the AWS WebSockets API).

The client will perform its normal SignalR request to AWS WebSockets API which will then forward the HTTP request to the Lambda function (with the connection id) which would route this request to the appropriate Hub and the Hub will immediately respond to the connection id with the result.

I have started to look at the Microsoft.AspNet.SignalR source code here https://github.com/SignalR/SignalR

Is anyone here more familiar with this code and could help point me to some locations to insert this new HttpTransportType?

Thanks for any assistance.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.