When test transport fires close event it should remove its stop function from socket's close event #6

Closed
flowersinthesand opened this Issue Jun 6, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@flowersinthesand
Member

flowersinthesand commented Jun 6, 2015

Now that it doesn't, if a socket fires close event, close method of transports used to find a working transport method is executed unnecessarily even though they are already closed. In case of HTTP transports, you can see invalid abort requests are performed. Each test transport should remove its stop function from socket's close event on its close event.

@flowersinthesand flowersinthesand added this to the 1.0.0-Alpha2 milestone Jun 6, 2015

@flowersinthesand flowersinthesand self-assigned this Feb 11, 2017

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