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.

Sign up for GitHub

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

Jump to bottom

ESP8266 module doesn't work with multiple connections #138

Closed
SpenceKonde opened this issue Apr 30, 2015 · 2 comments
Closed

ESP8266 module doesn't work with multiple connections #138

SpenceKonde opened this issue Apr 30, 2015 · 2 comments
Labels
High Priority

Comments

@SpenceKonde
Copy link
Contributor

If it tries, everything goes to hell, because the handlers (ie for "Unlink"/etc) don't have any provision for determining which socket they are associated with.
@gfwilliams
Copy link
Member

Yes, it's particularly bad design.

I wondered whether it was possible to just assume that the socket that data was last received on was the one that should be closed. Or maybe there's some kind of 'socket status' command that could be used to check which one had actually closed.

@gfwilliams
Copy link
Member

Should be fixed now - at least when using the newer ESP8266 firmware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
High Priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gfwilliams @SpenceKonde