I am not as familiar with the api's but it seems that the read and write distinction is somewhat parallel to the featuresource featurestore combination. I can see a reason to keep separate if we wanted to have a lightweight class for reading that reads versions but can't edit. This could be useful for audit and logging concerns. If it makes sense to combine that is fine in most cases if you are implementing one then you would be implementing both i suppose.
I have no problem with splitting featurelocking from featureversion. On 04/08/2011, at 7:07 PM, Jody Garnett wrote: > Interesting; thanks for writing that up. > > Would you like comments / discussion here on the email list or on GEOT-3770. > > For the FeatureDiff class; we already have a concept of that name in use > (used to store the differences for a Transaction commit() method call). Could > we call it a FeatureDelta? > > Thanks for the UML diagram; can we attach that to the wiki page or GEOT-3770 > (so we don't lose it over time). > > I think we could make the FeatureVersioning interface a sibling of > FeatureLocking (i.e. both extend FeatureStore). While an implementation may > choose to implement both we should set up the interfaces so they can choose > to implement one or the other (or both). > > If possible I would like to avoid getting a power set of classes; is there > any way we can avoid the difference between FeatureSourceVersioning and > FeatureVersioning? Only logic I could think of here would be that > FeatureVersioning only applies as an extension of FeatureStore (as without > the ability to edit something; how can there be more versions?). I suppose > that someone else can edit and you would like the ability to query history > etc.... I will check the WFS 2.0 spec to see if has any guidance on Query. > > Jody ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
