Closed GoogleCodeExporter closed 9 years ago
hmm, sorry, I can't understand what's the problem ? Is it something like the
following:
1, clear the cache,
2, wait - everything is refetched - hopefully
3, clear the cache
4, ???
Original comment by gzsom...@gmail.com
on 21 Oct 2008 at 8:27
4. wait - everything is refetched - hopefully
but instead you get
4, no wait, fast refresh but no refetch
Original comment by franci...@gmail.com
on 21 Oct 2008 at 8:39
I think, this bug, or feature is a result of the changes of the concepts. What
was
previously the 'cache', now becomes the 'database'. The difference between the
two is
the following, if you clear the cache, you can easily re-generate it's content,
from
the existing datas, but if you clear the database, you are lost. Or nearly lost
:)
This is needed, because we - or at least I - want to support a
disconnected/unmounted
operation mode. So the 'clear cache' menu doesn't clears the database - that
would
remove all of the informations about the currently unaccessible files, just
removes
from the UI, and starts a re-scan. After the file system scan, the old
ImdbCaller/MainServiceCaller detects that the found files match to one of the
movie
stored in the database, and associate it with again, with all the scoring/voting
informations. This is why it's fast :)
Original comment by gzsom...@gmail.com
on 21 Oct 2008 at 10:14
so what is the difference between the first and the second clear cache then?
Original comment by franci...@gmail.com
on 22 Oct 2008 at 6:31
Hmm. I don't know :)
Original comment by gzsom...@gmail.com
on 22 Oct 2008 at 10:26
I know now. Because of a missing 'Singleton' annotation, multiple XMLCache
object is
created, and only one is cleared.
Original comment by gzsom...@gmail.com
on 23 Oct 2008 at 1:52
great, I never thought about that
Original comment by franci...@gmail.com
on 23 Oct 2008 at 1:55
Original issue reported on code.google.com by
franci...@gmail.com
on 21 Oct 2008 at 6:07