Hi,
random thoughts :
Looking at DefaultFeature, I see the hash code is something like
hash(featureId, featureType). This means the hash code doesn't change when
one of the attributes is modified, although it would be nice if features
were immutable.
Using some other hash built on hash(featureType, featureId, attributes)
could ease tests like Feature.equals(Feature) or be used as a version
marker, since modifications would alter the hash signature. This could be
used to provide a version service on top of a datastore that does not
support versions, with a revision being the map of ids and hashes. At least,
it could help to answer the question 'what has changed since time t in the
datastore ?'.
I see also DefaultFeature references its parent FeatureCollection, which in
turn references other features. When caching features, this means we have to
keep in memory a lot of (possibly) unwanted features.
Cheers,
Christophe
-------------------------------------------------------------------------
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
