Skip to content
This repository has been archived by the owner on Mar 12, 2021. It is now read-only.

Implement long polling transport #62

Open
moozzyk opened this issue Dec 23, 2014 · 11 comments
Open

Implement long polling transport #62

moozzyk opened this issue Dec 23, 2014 · 11 comments
Milestone

Comments

@moozzyk
Copy link
Contributor

moozzyk commented Dec 23, 2014

No description provided.

@nicolasr75
Copy link

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
Copy link
Contributor Author

moozzyk commented Jun 3, 2015

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

@nicolasr75
Copy link

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

@muratg muratg added this to the Backlog milestone Sep 9, 2015
@matt14m
Copy link

matt14m commented May 24, 2016

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

@Sonic78
Copy link

Sonic78 commented Jul 15, 2016

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
Copy link

ghost commented Jul 28, 2016

@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
Copy link
Contributor Author

moozzyk commented Jul 29, 2016

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

@matelich
Copy link

matelich commented Mar 22, 2017

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
Copy link
Contributor Author

moozzyk commented Mar 23, 2017

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

@a-ilyin
Copy link

a-ilyin commented Aug 21, 2019

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
Copy link
Member

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants