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

Async API #47

Closed
niemyjski opened this issue Jan 11, 2016 · 5 comments
Closed

Async API #47

niemyjski opened this issue Jan 11, 2016 · 5 comments

Comments

@niemyjski
Copy link

The world we live in today is 100% async. I think that the whole api should be async and those who are needing non async can use wrappers around there code to make it sync.

This would also make the api more consistent because you can't currently do an async reverse geocode..

@chadly
Copy link
Owner

chadly commented Apr 2, 2016

Yes, I agree. I am planning a v4.0 to be released alongside .net core at which point I think introducing this API change makes sense.

@Dexyon
Copy link

Dexyon commented Dec 5, 2016

How is the progress on the .NET CORE ? I see your feature branch, but it seems a bit out of date..

@adamhathcock
Copy link
Contributor

Updated the feature branch in a PR if anyone is interested.

@mclang
Copy link

mclang commented Mar 17, 2017

Did I understood right: There is GoogleGeocoder.ReverseGeocodeAsync -function, but it doesn't work?

I'm trying to use F# Async Workflow to reverse geocode e.g 100 addresses, but the best queries per second I get is around 2.

Is there documentation how to make several parallel requests using Geocoding.net either with Task Parallel Library or or with Async Workflow?

@chadly
Copy link
Owner

chadly commented Jun 13, 2017

this is released in v4.0

@chadly chadly closed this as completed Jun 13, 2017
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

5 participants