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

workers + messaging tiles/models #2031

Closed
jimmont opened this issue Jan 30, 2016 · 1 comment
Closed

workers + messaging tiles/models #2031

jimmont opened this issue Jan 30, 2016 · 1 comment

Comments

@jimmont
Copy link

jimmont commented Jan 30, 2016

Would it make sense to use workers generally for all model operations, and make these workers more accessible, and does this overall reduce complexity and improve performance?

My guess is that having the worker manage/using transferable objects (#1504) would be key to making this efficient, at least from a ui-standpoint.

Several worker-related issues (#929 #1504 #899) overlap with a problem I'm tackling in cordova where tiles are provided by the filesystem (from the ui, for some reason the filesystem isn't available to workers) and am having to figure out passing the workers assets (via map.style.dispatcher). From this problem I started looking into how the tiles are loaded, workers and related messaging. Given the little I've read/understand of the source I'm not sure it makes sense but because it overlaps with open issues that are actively being solved I thought to ask.

@mourner
Copy link
Member

mourner commented Feb 1, 2016

Would it make sense to use workers generally for all model operations, and make these workers more accessible, and does this overall reduce complexity and improve performance?

I don't understand what this would mean, can you provide a simple example?

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

4 participants