Implement long polling transport

[moozzyk]

No description provided.

[nicolasr75]

I have successfully used SignalR-Cpp to connect some C++ applications to an ASP.NET web application with IIS 8. It works really great! It would be even better if I could support some existing installations with IIS 7.5 which does not have web sockets. Are there any plans to support the long polling transport in the near future?

[moozzyk]

@nicolasr75 we don't have any specific timeline at the moment.

[nicolasr75]

OK. Thanks anyway, I think you did a great job with this project!

[matt14m]

Any update on long polling? We've got web sockets doing great things but need to support older OS's / servers.

[Sonic78]

Any update on long polling? We know of many scenarios where firewalls will not allow an upgrade of the http connection to WebSockets so we need the possibility to use a fallback or SignalR is no alternative for us?

[ghost]

@moozzyk Do you happen to have a rough estimate of how much effort it would be to support Long Polling? We'd urgently need a native SignalR client with fallback support, and we'd think about implementing it ourselves.

[moozzyk]

My rough estimate would be ~2 weeks but I think there might be a few tricky spots.

[matelich]

I see some work (aspnet/SignalR-Client-Cpp@4eabfb4) has been done since your last comment here. I assume that was just a small bit of work against the 2 week estimate?

[moozzyk]

Yeah. I started looking at this some time ago but have been busy with other things.

[a-ilyin]

Hello, everyone.
I suppose all the code moved to https://github.com/aspnet/SignalR-Client-Cpp and no progress will be done here.
Am I right?
Any chance long polling transport to be implemented?

[BrennanConroy]

This Repo is for ASP.NET SignalR and will likely have very little code changes in the future.

Work on the new client for ASP.NET Core SignalR is located at the repo you linked.