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

Consider support/handling of System.Net.ClientWebSocket #780

Closed
DaniilVeriga opened this Issue Dec 22, 2015 · 1 comment

Comments

Projects
None yet
3 participants
@DaniilVeriga
Contributor

DaniilVeriga commented Dec 22, 2015

http://forums.bridge.net/forum/general/open-discussions/1320

Some basic support for System.Net would be helpful along with System.Net.WebSockets

For System.NET I am mainly missing the URI class. I think the ClientWebSocket class can simply wrap the built in browser WebSocket as it doesn't implement non-async members.

Relates to #776.

Implementation details:
MSDN ClientWebSocket Class

Underlying implementation according to MDN WebSockets

Includes a basic implemetation of System.Uri class

@LeonidVeriga

This comment has been minimized.

Show comment
Hide comment
@LeonidVeriga

LeonidVeriga Jun 4, 2016

MSDN ClientWebSocket Class

Underlying implementation according to MDN WebSockets

LeonidVeriga commented Jun 4, 2016

MSDN ClientWebSocket Class

Underlying implementation according to MDN WebSockets

@LeonidVeriga LeonidVeriga changed the title from Consider support/handling of System.Net to Consider support/handling of System.Net.ClientWebSocket Jun 4, 2016

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