I would go with the first for the same reasons already listed. The API
was looking for feedback from others on how it would be used, so it's
not really nailed down.
While I'm listed as the maintainer of this module, no major work has
been done in it for about year. I don't think many people are using
this API yet so changing it to improve it probably won't affect many people.
Graham.
Justin Deoliveira wrote:
>
>> The solution suggested in the thread was to make a factory
>> that can bear multiple algorithms. I see two paths ahead:
>> - change the whole ProcessFactory definition so that
>> it returns a list of process names, and takes a name
>> parameter in each call (api break)
>> - create a new CompositeProcessFactory that is defined as:
>>
>> CompositeProcessFactory {
>> Set<String> getProcessNames();
>> ProcessFactory getProcessFactory(String name);
>> }
>
> I would go with the first. The second seems like a workaround holes in
> the api... and since the api is not really that stable as of yet, I
> would opt for just changing it.
>
> 2c.
>
> -Justin
>
--
Graham Davis
Refractions Research Inc.
gda...@refractions.net
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
