signalr.client

This is a "hello world" app but I can't find the solution. This is the code on the client: public class MainActivity extends ActionBarActivity { HubProxy proxy; EditText messageText; TextView resultText; @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); Platform.loadPlatformComponent(new AndroidPlatformComponent()); //Setup connection String server = "http://10.0.2.2:8081/"; HubConnection connection = new HubConnection(server); proxy = connection.createHubProxy("chatHub"); Toast.makeText

Is possible to connect using Javascript client to more than one SignalR servers? For example: <script type="text/javascript"> $.connection.hub.url = 'http://server1.net/signalr'; var server1Hub = $.connection.server1Hub; $.connection.hub.start().done(function () { }); // i need to connect to server2 $.connection.hub.url = 'http://server2.net/signalr'; var server2Hub = $.connection.server2Hub; $.connection.hub.start().done(function () { }); </script> Trying to connect (again) the second time gives me an error: 'server1Hub' Hub could not be resolved. Can i create two instances of $.connection ?

I have a .Net Windows Service (client) that's communicating with a SignalR Hub (server). Most of the client methods will take time to complete. When receiving a call from the server, how do I (or do I need to) wrap the target method/hub.On to avoid the warning: "Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the await operator to the result of the call" On the client, this is a sample of the start up / setup code: IHubProxy _hub string hubUrl = @"http://localhost/"; var connection = new HubConnection(hubUrl, hubParams

I'm using long polling with SignalR. I've found that user session ends (ASP.NET Session_End is being called) right after singalr based webpage makes /signar/ping request ( as shown in this screenshot ). I went through http://www.asp.net/signalr/overview/signalr-20/hubs-api/handling-connection-lifetime-events but couldn't figure out clear answers following questions. How to keep ASP.net user session alive from a signalr client webpage? What is the actual purpose of /ping? Is the timing for this /ping call configurable? The entire purpose of the /signalr/ping request is to keep ASP.NET sessions

By default, there are a default of 1,000 messages stored in the ring buffer on the server. It doesn't make sense for me to send a lagging client 1,000 updates, but rather just the most recent update. In WCF I can do this by using volatile data. I suppose I can emulate a volatile approach by reducing the buffer to "1", but not sure if this can be configured on a per hub basis, or ideally, on a per method basis. Does it matter if I use hubs or persistent connections with this? Even if you set the DefaultMessageBufferSize to 1, SignalR ensures each buffer will hold at least 32 messages. The

I'd like to improve the resilience of my clientside implementation of a signalR client. Currently, I do this: hub.server.sendClientNotification(string, appSettings.username()); However occasionally, an exception related to connectivity is thrown because either the server is not responding or the client's internet connection has become unusable. I'd like to solve this by queuing up requests and then doing something like this: try { // pop from queue hub.server.sendClientNotification(string, appSettings.username()); // success - discard element } catch (e) { // requeue element } With this kind

I've written a small echo-server (.net 4.5), console client (.net 4.5) and web client using SignalR and example presented here . Server is hosted in IIS8/Win8. Then I ran both clients on Win7. and I see that web client in Chrome uses webSockets, while console app client uses serverSentEvents. If I run console client on Win8, then webSockets transport is in use. Is it true that SignalR .NET client will use webSockets only on Win8 and higher? It's correct: .NET client uses WebSockets only on Win8 and higher. For a project I had to use real websocket connections in combination with SignalR. For