SignalR is a platform to real time communications. When you begin creating apps go like a shot, and the truth is that the level of abstraction that gives you is great. Customers .net having to WPF, Win8 and Html work seamlessly, however (isn’t a but) If you think app Windows Phone (8.1 for example), you can find with the strange situation in which the emulator everything is perfect and in the device, not so much.
Note, is not not work but that messages are quite slow in coming (from 5 seconds up to minutes). The test scenario also includes complex authentication methods, is a Website of Azure, which plays the role of SignalRHub.
If we activate the trace in the WP client we can see that the pattern of behavior of the connection is
Connecting, Connected, Reconnecting, Connected, Reconnecting, Connected,…
In few seconds the client connects and disconnected several times. This leads us to think that management of connections (ping that bad say you) it may be wrong, and that the solution is to change the type of transport.
Messages are delayed when using server sent events on Silverlight. To force long polling to be used instead, use the following when starting the connection:
Luckily this solution works also for Windows Phone apps. Now, if you see why this type of transport if works, intuition leads you to MSDN. The amazing thing is that this class is not documented or anything like that (link)
So now using touch using LongPollingTransport() , wait for the friends of MSDN to complete documentation or view within the code of SignalR operation of this kind.
Those options or… use a debugger such as Fiddler to make differences there are between the transport by default and LongPollingTransport. But that is for another post
Greetings @ Somewhere around