I have not done any work yet - I am getting the names in order first so that we can have sane conversations over email.
I understand what you are saying; the part I miss is this - why is the separation into two classes useful? - createBackingStore - is used by all the createFoo(...) methods when they get a cache miss, the contract says a AuthorityFactory will be returned (I would like to enforce that as a DirectAuthorityFactory so we are explicit and do not get buffered on buffered action). This contract is the same for both classes on the table; the code will be the same at the end of the day; are you wanting to change the configuration parameters of the pool? So BufferedAuthorityFactory only keeps one worker (ie a single BackingStore) and ThreadedAuthorityFactory has access to many? What use case is confused or gotten in the way of here? You seem to find the idea of buffering important ... perhaps picturing BufferedAuthorityFactory as a simple wrapper around a backing store. I assure you it is far from a simple construct as the number of issues arising from the idea are many and far reaching...even when we restrict outself to one. Jody > Jody Garnett a écrit : >> So the code is the same in both cases? > > Yes but not repeated. It is repeated for now because I didn't wanted > to break the work you may be doing right now on > ThreadedAuthorityFactory. But if ThreadedAuthorityFactory extends > BufferedAuthorityFactory, it would override *only* > get/createBackingStore(). All the cache management (i.e. all > 'createFoo(...)' methods) would be inherited from > 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 Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
