Martin Desruisseaux a écrit :
> In my "history fix" round, I restaured BufferedAuthorityFactory as it was
> before
> ThreadAuthorityFactory and as an independent class (not a subclass of
> ThreadedAuthorityFactory). This is because I feel that ThreadAuthorityFactory
> could be a subclass of BufferedAuthorityFactory and just override the
> 'getBackingStore()' method. We may talk about that later - it doesn't impact
> your development in short term on ThreadedAuthorityFactory.
I means, we could apply on BufferedAuthorityFactory the same changes (using the
object cache) that you applied on ThreadedAuthorityFactory. But by preserving
BufferedAuthorityFactory in its current state (for now), we avoid that such
change (if we decide to apply it) appears in the history as a whole block
deleted, then a whole block inserted.
ThreadAuthorityFactory would just override 'getBackingStore()' with something
more elaborated than returning a constant backing store. The object cache
mechanism after that would be the same.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
