Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

WIP: uasyncio.websocket: Websocket implementation for uasyncio. #228

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

Closed
pfalcon wants to merge 3 commits into micropython:master from pfalcon:uasyncio-websock

Conversation

@pfalcon
Copy link
Contributor

@pfalcon pfalcon commented Nov 3, 2017

Q #1: Should this be in uasyncio package at all? Upstream doesn't have
this. Pro: will be easier for people do discover (see e.g.
#148)

Q #2: This provides implements 2 ways to create a WS connections:

  1. using start_ws_server(); 2) using wrapping existing StreamReader
    and StreamWriter. History: initial prototype of course used 2). But
    the idea was "it should be like the official start_server()!!1". But
    then I though how to integrate it e.g. with Picoweb, and became clear
    that 2) is the most flixble way. So, 1) is intended to be removed.

Q #3: Uses native websocket module for read path, but has own
write path due to micropython/micropython#3396

Q #4: Requires #227
due to micropython/micropython#3394 .

hiway reacted with hooray emoji
Paul Sokolovsky added 3 commits November 3, 2017 21:49
Q #1: Should this be in uasyncio package at all? Upstream doesn't have
this. Pro: will be easier for people do discover (see e.g.
micropython/micropython-lib#148)
Q #2: This provides implements 2 ways to create a WS connections:
1) using start_ws_server(); 2) using wrapping existing StreamReader
and StreamWriter. History: initial prototype of course used 2). But
the idea was "it should be like the official start_server()!!1". But
then I though how to integrate it e.g. with Picoweb, and became clear
that 2) is the most flixble way. So, 1) is intended to be removed.
Q #3: Uses native websocket module for read path, but has own
write path due to micropython/micropython#3396
Q #4: Requires micropython/micropython-lib#227
due to micropython/micropython#3394 .
Copy link
Contributor Author

pfalcon commented Nov 3, 2017

Copy link
Contributor Author

pfalcon commented Feb 1, 2018

Merged.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

AltStyle によって変換されたページ (->オリジナル) /