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

Start using Webworkers for big jobs #223

Open
nickpeihl opened this issue Oct 28, 2015 · 6 comments
Open

Start using Webworkers for big jobs #223

nickpeihl opened this issue Oct 28, 2015 · 6 comments

Comments

@nickpeihl
Copy link
Member

Webworkers appears to be a way to avoid locking the browser by threading JavaScript jobs. Can we use them with Turf.js? Sometimes I have a big appetite and would rather not lock my browser while chopping.

@mapsam
Copy link
Member

mapsam commented Oct 28, 2015

Ah yes, this has come up in #127 as well. I'm not terribly familiar with workers so would love some direction here!

@nickpeihl
Copy link
Member Author

Unfortunately, I'm not familiar with it either. But I wouldn't mind tackling it after I finish arcgis-feature-services.

@mapsam mapsam changed the title Can we use Webworkers with Turf for big processing jobs? Start using Webworkers for big jobs Oct 28, 2015
@mapsam
Copy link
Member

mapsam commented Oct 28, 2015

Bam! Looking forward to seeing what it's all about 👯

@jczaplew
Copy link
Contributor

This seems like a good place to get started with webworkers - http://catilinejs.com/

@nickpeihl
Copy link
Member Author

Turf-Async is a demo of how I'd expect this to work. I'll try to add more documentation this weekend.

@aaronr
Copy link
Member

aaronr commented Feb 19, 2016

Oh... this is cool. I will take a look, but thanks for posting this!

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

No branches or pull requests

4 participants