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

Use new chrome.sockets.* APIs #1

Closed
feross opened this issue Mar 4, 2014 · 7 comments
Closed

Use new chrome.sockets.* APIs #1

feross opened this issue Mar 4, 2014 · 7 comments

Comments

@feross
Copy link
Owner

feross commented Mar 4, 2014

Note: Starting with Chrome 33, this API is deprecated in favor of the sockets.udp, sockets.tcp and sockets.tcpServer APIs.

@feross
Copy link
Owner Author

feross commented Mar 4, 2014

@quartzjer
Copy link

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 :)

@feross
Copy link
Owner Author

feross commented Mar 5, 2014

@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.

@quartzjer
Copy link

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...

@feross
Copy link
Owner Author

feross commented Mar 6, 2014

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.

@feross
Copy link
Owner Author

feross commented Mar 16, 2014

Okay, this is done now. See 5760ef1 for the code changes. Published as chrome-dgram@2.0.0.

Working on the same change to chrome-net as well. Expect that shortly.

@feross feross closed this as completed Mar 16, 2014
@feross
Copy link
Owner Author

feross commented Mar 16, 2014

And now chrome-net is 2.0.0 as well: feross/chrome-net#5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants