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.
That way, we get separation of concern (buffer vs thread). It also make more
obvious that ThreadedAuthorityFactory is buffered. Also, I'm not sure that
"ThreadedAuthorityFactory" was a better name than "BufferedAuthorityFactory"
because I believe that a majority of users will care more about buffering than
concurency (BufferedAuthorityFactory already handle many threads asking for a
same small set of CRS. ThreadAuthorityFactory handle many threads asking many
different CRS, which should be a less common case I think).
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
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
