[OpenStreetMap] #4501: Include API usage policy technical limitations into Capabilities

Frederik Ramm frederik at remote.org
Tue Jul 31 18:57:36 BST 2012


Hi,

On 07/31/12 19:13, OpenStreetMap wrote:
> #4501: Include API usage policy technical limitations into Capabilities

[...]

>   We are currently working on a change in JOSM in order to download data
>   with several concurrent threads, up to to the maximum number allowed by
>   the OSM API usage policy (currently 2):

My suggestion: Reduce maximum number allowed to 1, and save you the hassle.

Assuming that the API is not idle, I think any multi-threading 
performance gain on the client side is at the expense of other clients 
who then have to wait longer.

I think everyone should just use API connection at a time.

If performance gains are possible by querying the database in parallel, 
then these could be implemented in the API itself (thereby benefiting 
all users and not only those of one specific editor).

I like the general idea of adding policy stuff to the capabilities 
response (see 
http://wiki.openstreetmap.org/wiki/User:Frederik_Ramm/Ideas_for_API_0.7#Extend_.22Capabilities.22_Response_with_Policy_Information 
which I incidentally wrote only recently), but I don't like the idea 
that some clients should grab a larger share of API resources than others.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"



More information about the rails-dev mailing list