Skip to content

Conversation

@konstantinzolotarev
Copy link
Contributor

No description provided.

@konstantinzolotarev
Copy link
Contributor Author

Related to #488

transport.supportsBinary = false;
} else {
transport.supportsBinary = true;
try {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this try..catch needed here? Is there a particular issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was not sure but in https://github.com/socketio/engine.io/blob/master/lib/server.js#L299
Same statement wrapped in try..catch so I did same.

@darrachequesne
Copy link
Member

Is the debugError actually needed in lib\server.js? I think it might make sense in lib\socket.js, in order to split received/sent messages (how about naming it trace()?) from transport details. What do you think?

@konstantinzolotarev
Copy link
Contributor Author

@darrachequesne Yep make sense. Will continue then. This PR Could be closed.

darrachequesne added a commit that referenced this pull request May 8, 2020
This reverts commit 2c55b27, which breaks websocket transport under node v0.10 (#494).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants