-
Notifications
You must be signed in to change notification settings - Fork 156
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
Comments
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. |
How is the progress on the .NET CORE ? I see your feature branch, but it seems a bit out of date.. |
Updated the feature branch in a PR if anyone is interested. |
Did I understood right: There is 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? |
this is released in v4.0 |
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..
The text was updated successfully, but these errors were encountered: