[Milhouse]

Your old poster is still in the cache after the movie is removed, so when the movie is added back you still have your old poster.

It would be necessary to remove all artwork from the cache of the movie being removed from the library, or forcibly re-cache the movie after it has been added back, both of which are possible but would massively slow down qax (and may not be desirable behaviour for all users). In addition, although the cache of the client on which you run the qax option would be correct (ie. the local cache now contains the new artwork), you'd still have the old artwork present on all your other clients as their cache would still be stale, and you'd need to refresh their cache individually ("C movie" etc.), so maybe a better cache pre-load option is required.

I'm thinking a cache pre-load option which compares the timestamp from the cache (lasthashcheck, or failing that lastusetime) against the modification date of the artwork file, and reloads the artwork if the modification time is more recent.

With such a change, you would run qax (reload movie, nice and quick) followed by re-cache of any artwork that is now stale in the cache (and you'd need to repeat just the re-cache step against all of your other clients). Alternatively much like qa.nfo.refresh, specify a relative date/time period and re-cache any artwork modified within that period, but right now I'm thinking the timestamp comparison method will be more useful.

Edit: Acquiring the modification timestamp of remote (http://) artwork isn't going to work, whereas specifying a relative date/time period will work for both local and remote artwork... so something like cache.refresh=today|#|date-time should work (and will be quicker too - obtaining the modification date for all local files would have been pretty slow...).

The cache.refresh modifier would only apply to the "C" and "nc" options, as it will restrict the artwork that is to be removed and reloaded, and would have no effect on the "c" option.