Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transports need to send "Keep Alives" #168

Closed
ielbury opened this issue Jan 31, 2012 · 3 comments
Closed

Transports need to send "Keep Alives" #168

ielbury opened this issue Jan 31, 2012 · 3 comments
Assignees
Milestone

Comments

@ielbury
Copy link

ielbury commented Jan 31, 2012

In order to better support traversing network equipment that perform an kind of proxy function such as load balancers, UTM (Unified Thread Managment) appliances/software, proxy servers etc, a "keep alive" is required to keep the connection open.

@ielbury
Copy link
Author

ielbury commented Feb 4, 2012

The current time-out mechanism makes the streaming protocols no different then long polling given the dynamics and payload.

Until this issue is resolved, users will likely be better off with a long polling solution.

@ielbury ielbury closed this as completed Feb 4, 2012
@davidfowl
Copy link
Member

You can make the timeout infinite if you wanted to simulate the old behavior. We'll look at keep alive in the next release.

@ielbury ielbury reopened this Feb 4, 2012
@ghost ghost assigned davidfowl Mar 8, 2012
@davidfowl
Copy link
Member

Fixed in 832383d.

You can set the KeepAlive property on the ConfigurationManager and SignalR will send an empty frame of data (based on the transport) on the specified interval to keep the connection alive.

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

No branches or pull requests

2 participants