Jul 24, 2015 06:51 PM|qingl77|LINK
My message sent a week ago is still waiting for answer: In the Microsoft "Introduction to SignalR scale out" article, it states
"With a backplane enabled, each application instance sends messages to the backplane, and the backplane forwards them to the other application instances."
In my test, this "backplane enabled" for a particular SignalR server instance in Azure Cloud (a WebRole) means to have at least one SignalR cleint connecting to that instance. This may be a problem when an instance without any SignalR client connected receives
HTTP request designated to a SignalR client connected by other instance of the same Web Role. Backplane will simply not do routing.
My question is: is there some configuration (maybe in server code) to make all of SignalR server instances "backplane enabled" without relying on those instances connected by SignalR client?