Preamble
My current employer is leaning towards the revamp of our outdated codebase (we still have some .NET 2.0 code up and running but starting to suffer from deprecation), and as part of this effort our team is choosing some technologies and practices to adopt as our base framework for new and updated applications - and quite a few deal with the UI, such as three.js, D3js (we have our healthy share of data visualization), semantics and websockets; the latter brought us to SignalR.
While researching the way SignalR is implemented (and websockets in general), I reached a point where I wanted to check if multicast-like communication would be viable. (In simple terms, a multicast is similar to a broadcast in the sense that you can send a single packet simultaneously to several clients - difference being that you may control how many clients are part of the whole exchange, by having them join a given multicast group).
Multicast is a very neat technology if you want to save bandwidth - and, I imagine, processor time in SignalR's case.
So far, all implementations of multicast-like behavior using SignalR that I've managed to check kind of behaves the same way, iterating through all pre-established connections. I've also checked the documentation, but nothing noteworthy came up so far.
That said,
Question
Is SignalR compatible with TCP Multicast? Have anyone implemented a similar scenario?