Discover which endpoints are associated with SignalR hubs

[Ninds]

Hi,
Is it possible to discover at runtime which endpoints exposed by one's own kestrel service are actually endpoints associated with SignalR hubs ?

Context

The setup is described at davidfowl/BedrockFramework#65
To summarize :
The service is setup to handle multiple protocols of which one is HTTP. The service is also setup with a (main) Controller AssemblyLoadContext and some worker AssemblyLoadContexts. The controller ALC encapsulates an instance of Kestrel wired up to a socket. The worker ALCs each encapsulate an instant of Kestrel listening on a MemoryTransport.
Upon receiving requests, the Controller Kestrel dispatches (most but not all) requests internally to one of the worker Kestrels hosted in their own isolated ALCs. The main purpose/motivation for this choice of design is that the code servicing the requests cannot be guaranteed to be thread-safe and hence this particular implementation of isolation/sandboxing has been chosen.
This setup works well in that it meets it's requirements and expectations.

I would however like to extend this framework to facilitate SignalR. I think it would be more appropriate for the hubs to hosted inside the controller Kestrel (or at least in a dedicated ALC/Kestrel per hub type) . To then dispatch a request to a worker Kestrel/ALC or process it in the controller Kestrel, the code would have to analyse whether the incoming request is headed for a SignalR hub or not.

Thanks
N

[Ninds]

I think:
EndpointDataSource
Endpoint.Metadata
HubMetadata

Should do the trick.

[BrennanConroy]

Haha, I was just about to answer with some of those links.

You'll also probably want to look for NegotiateMetadata as well since it is for the /hub/negotiate endpoint

aspnetcore/src/SignalR/common/Http.Connections/src/ConnectionEndpointRouteBuilderExtensions.cs

Line 101 in 4b796c7

negotiateBuilder.WithMetadata(new NegotiateMetadata());

[Ninds]

Thanks. It's working nicely.

...probably want to look for NegotiateMetadata as well..

It wasn't necessary since HubMetadata covered the negotiate ones too.