-
Notifications
You must be signed in to change notification settings - Fork 571
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
clear writeBuffer in each drain
+ clear writeBuffer after nextTick
#95
Conversation
add new test for clean writeBuffer in nextTick.
var engine = listen({ allowUpgrades: false }, function (port) { | ||
// hack to access the sockets created by node-xmlhttprequest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you undo this test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change was needed when we upgraded node-xmlhttprequest
to 1.5.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry. I think I have some conflicts in my github repository, let me check it again.
Ok, conflicts resolved. Please check them again. |
@@ -24,6 +24,7 @@ function Socket (id, server, transport) { | |||
this.readyState = 'opening'; | |||
this.writeBuffer = []; | |||
this.packetsFn = []; | |||
this.packetLengths = []; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order to keep packets length
close also if socket.readyState is on "opening"
This pull request contains new changes for issue #89 and issue #59.