Jody Garnett a écrit :
> The problem is these are identical in implementation: even for case of a
> single worker I am going to store it in an ObjectPool so I can can
> remove all the Timer concerns about evicting the backingStore. I need to
> show that am doing what we are paid for - making GeoTools referencing
> module handle multiple threads (and basically scale). A class name helps
> me make that point in a clear way everyone can see on a class diagram.
I was suggesting to declare "ThreadedAuthorityFactory" as a subclass of
"BufferedAuthorityFactory", overriding the 'getBackingStore()' or
'createBackingStore()' method (not sure which one). So both names are there and
ThreadedAuthorityFactory leverage all ObjectPool caching performed by
BufferedAuthorityFactory.
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
