Hi Richard,
I don't think without more information it's clear precisely what QGIS
should change to help them?
Indeed, personally I'm still not sure what the current problem is for
them. I get that they have some over-users of their service and need to
curtail this (a very tricky problem), but what's their current solution
and how does a user-agent change help it?
I'd suggest against QGIS using different user-agents for destinations as
was suggested earlier in the thread because down that road lies madness
(it's a highly opaque thing that /will/ bite people as they try and
debug issues).
Cheers,
Jonathan
On 23/02/2019 11:17, Richard Duivenvoorde wrote:
For what I understand, they use some cookie-based trick to help maintain
their QOS (and then to make it possible to throttle a very demanding web
application?).
This made sense to me. Also because I really do not envy maintainers of
such services: it is hard to keep up such free services (as an example
(see irc log) he mentioned that certain transportation software started
to poll the reverse geocoding every second in every car). I think it's
pretty important for us to have OSM, and be helpfull to them.
But if Firefishy/Grant is willing to give more details (he is in bcc)
that would be great.
Regards,
Richard
_______________________________________________
QGIS-Developer mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
