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.

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

Node-like UDP/TCP abstraction for Chrome Apps #7

Closed
feross opened this issue Nov 9, 2013 · 1 comment
Closed

Node-like UDP/TCP abstraction for Chrome Apps #7

feross opened this issue Nov 9, 2013 · 1 comment
Assignees

Comments

@feross
Copy link
Member

feross commented Nov 9, 2013

Currently working towards this here: https://github.com/feross/chrome-app-socket

Reasons to make it like dgram and net in node:

  • re-usable for others via browserify
  • familiar, understood semantics
  • tcp implementation uses streams
  • might be able to re-use existing node bittorrent modules that assume dgram and net api

Issue is here: https://github.com/feross/chrome-app-socket/issues/1

@feross
Copy link
Member Author

feross commented Nov 10, 2013

This is finished. See: chrome-app-socket

From the Readme:

chrome-app-socket lets you use the Node.js net (TCP) and dgram (UDP) APIs in Chrome Packaged Apps.

Instead of learning the quirks of Chrome's chrome.socket API for networking in Chrome Apps just use the higher-level node API you're familiar with. Then, compile your code with browserify and you're all set!

This is a meta-package that just wraps chrome-dgram and chrome-net.

@feross feross closed this as completed Nov 10, 2013
@ghost ghost assigned feross Nov 10, 2013
@lock lock bot locked as resolved and limited conversation to collaborators May 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant