id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
23645	[patch] ChangesetCache: Is it useful as it is? Why isn't it always used?	GerdP	team	"Just some thoughts...
We have a lot of dialogs which handle changeset data, but only some use the in-memory cache implemented with class `ChangesetCache`. I wonder if this is intended or not. We also have a lot of different implementations to download changeset data.
We have at least three dialogs:
- History Browser (`HistoryBrowserDialog`)
- Changeset Manager (`ChangesetCacheManager`)
- Changesets side pane (`ChangesetDialog`)
Each seems to implement methods to download changeset data and some seem to use multifetch ignoring the cache while others use the cache but fill it only with singe GET requests. 
Quite confusing!
Esp. the Histoy Browser bypasses the cache and possibly downloads huge amounts of data, e.g. when the user browses the history of a complex route relation with many members and many versions.

Besides that we have the reverter plugin which implements its own set of tasks to download history data and I think it also always bypasses the cache.

My conclusion so far: The cache is not very useful as it is, but a better implementation using a disk cache could help to prevent hitting the rate limits."	task	closed	normal	24.06	Core		fixed	changeset cache