-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Use new chrome.sockets.* APIs #1
Comments
Funny timing, I was just looking to use this package and wondering what the state was w/ the 33 updates, sounds like it's definitely going to get updated :) |
@quartzjer Neat, what are you thinking about using this for? Really curious. Also, do you know if there's been an announcement about the changes? I only noticed the new API on the developer site and skimmed it. It doesn't seem substantially different but yeah, I want to use the latest. |
I'm overhauling the telehash javascript (https://github.com/telehash/thjs) to be all browserify based (SO much cleaner!), and want to dump the udp-via-chrome mishmash I did to use this instead :) I know the broke/updated many or most of the other system apis (like serial/usb) w/ 33, not sure where the "dev community" discussion happens tho... |
I worked on this tonight. It's not quite finished. For tcp at least it turned out to be more tricky than I expected because they changed quite a bit. |
Okay, this is done now. See 5760ef1 for the code changes. Published as Working on the same change to |
And now |
Note: Starting with Chrome 33, this API is deprecated in favor of the sockets.udp, sockets.tcp and sockets.tcpServer APIs.
The text was updated successfully, but these errors were encountered: