We have C# application using SignalR and Amazon's ElastiCache as backplane. However even SignalR allows to mask out certain commands it stills sends a CONFIG to the ElastiCache which fails SignalR silently (CONFIG is not supported by ElastiCache). For now we compile our own binary of SignalR with the change of removing the auto reconfiguration routine.
I wonder if anyone else tripped over this issue and wanted to see how you solved it.
The best idea would be to write a proxy for ElastiCache (like the Twitter proxy) but that is a huge undertaking.
Thanks in advance.
In this case client is important and Baking your own SignalR definitly bad practice. Did you check this page http://www.asp.net/signalr/overview/performance/scaleout-with-redis: This method uses StackExchange.Redis(StrongName) and StackExchange.Redis has many options for connection.
We are using same method described in the page on AWS with Elasticache Redis and we don't have any issues you had...
Regards...