Fallback doesn't work with websockets in JS client. #1145

Closed
davidfowl opened this Issue Dec 15, 2012 · 3 comments

Comments

Projects
None yet
3 participants
@davidfowl
Member

davidfowl commented Dec 15, 2012

The scenario is we choose websockets, we start a new websocket but it just hangs and the connect event of the socket is never raised, so the signalr connection stays stuck. We should probably have a timeout here we check against.

@ghost ghost assigned NTaylorMullen Dec 15, 2012

@DamianEdwards

This comment has been minimized.

Show comment Hide comment
@DamianEdwards

DamianEdwards Jan 11, 2013

Member

This is lame but we can look at this after 1.0. Only affects situation where websocket request actually hangs for some reason without failing.

Member

DamianEdwards commented Jan 11, 2013

This is lame but we can look at this after 1.0. Only affects situation where websocket request actually hangs for some reason without failing.

@davidfowl

This comment has been minimized.

Show comment Hide comment
@davidfowl

davidfowl Jun 25, 2013

Member

@NTaylorMullen this can be closed right?

Member

davidfowl commented Jun 25, 2013

@NTaylorMullen this can be closed right?

@NTaylorMullen

This comment has been minimized.

Show comment Hide comment
@NTaylorMullen

NTaylorMullen Jun 25, 2013

Contributor

@davidfowl yup!

Contributor

NTaylorMullen commented Jun 25, 2013

@davidfowl yup!

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