Andrea, have you considered other patterns for capabilities, such as a property container, like Hints, or the GeoAPI UserData map? This would make it easier for users to add new capabilities without changing the Java API. In effect, this would be a more dynamically typed approach, which would be good as it is easier to extend, but bad because different communities can invent different ways of doing the same thing. Your proposal would keep implementations unified.
Either approach would be an improvement on the present instanceof + try/catch antipattern, so I support this change. Kind regards, Ben. On 27/04/10 01:34, Andrea Aime wrote: > Hi PMC, > since this is "proposal day" let me provide you with another one > that sums up part of the discussion of the last week about a > capabilities API in GeoTools: > > http://docs.codehaus.org/display/GEOTOOLS/Datastore+capabilities+API > > Opinions and votes welcomed > > Cheers > Andrea > -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
