Okay; let us get this one moving.
I ambushed aaime on his weekend to see if this was slated for gt-api as a
simple patch; or if it would go through the proposal process.
My initial thought was that this should be handled in a similar fashion to the
other marker interface we have in there:
> public interface BoundedSpatialOperator extends SpatialOperator {
> }
This is a marker interface used on spatial filters that can be optimised with a
bounding box query up front.
With that in mind I was thinking of:
package org.opengis.filter.expression;
public interface VolitileFunction extends Function {
}
Q: Why gt-opengis?
A: It is next to the other filter stuff and thus can be easily found; there are
already marker interfaces present so it is in good company
Q: Isn't this just an implementation detail that can be placed in gt-main?
A: No; we need to commit to it as public api; so implementations can
communicate to us how their function is to be used?
Jody
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
