Opened 13 years ago
Last modified 7 years ago
#7140 new enhancement
Improvements for /capabilities at startup
Reported by: | bastiK | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | api capabilities blacklist | Cc: | framm |
Description
At the moment, there is no reason for the /capabilities
request when JOSM starts. The intention is to read a blacklist like this one, but openstreetmap.org doesn't provide it at the moment. Here is a list of improvements, that would make this feature more transparent:
- Fix timeout - at the moment JOSM can freeze for minutes, when there is a slow network connection (see #6823).
- Don't run the request in main or event dispatch thread - should be done in the background.
- For each server URL remember whether it serves a blacklist. Skip the request at start if it doesn't. (This information can be refreshed, when it is older than 2 months.)
- Cache the capabilities locally. Only request at start when cache is missing or older than one week.
Attachments (1)
Change History (13)
comment:1 by , 13 years ago
by , 13 years ago
Attachment: | 7140_cache.patch added |
---|
comment:2 by , 13 years ago
Summary: | Improvements for /capabilities at startup → [Patch] Improvements for /capabilities at startup |
---|
Patch attached for caching the capabilities using CacheCustomContent
. Please take a look at it.
comment:4 by , 13 years ago
comment:6 by , 13 years ago
Summary: | [Patch] Improvements for /capabilities at startup → Improvements for /capabilities at startup |
---|
:-)
comment:7 by , 13 years ago
comment:8 by , 13 years ago
Cc: | added |
---|
Yes, 1. and 2. is a bug. (Point 3 is probably not so important, now that we have one week cache.)
There was a suggestion to serve the blacklist as part of the MotD. It seems that MotD is loaded in the background, so 2. might be solved in the process.
comment:11 by , 7 years ago
Keywords: | api capabilities blacklist added |
---|---|
Type: | defect → enhancement |
comment:12 by , 7 years ago
Close the ticket?
The question is if special care for blacklists makes any sense any longer. It only contains Google for a long time and Google does no longer use TMS, so Google layers can't be used with JOSM anymore at all as far as I know.
This could be implemented without big efforts using
CacheCustomContent
.