Hi all, at Geoserver we are working on developing a versioned WFS-T extension which, at first, should provide single branch versioning with history, attribution and rollback. Here I have written down the results of my research (warning, big document):
http://docs.codehaus.org/display/GEOS/Versioning+WFS and here is the first implementation proposal (much smaller): http://docs.codehaus.org/display/GEOS/Versioning+WFS+-+Phase+one+implementation+proposal Geotools already has a datastore, and uDig is using it to provide editing. I'd like to hear feeback from anyone interested, especially on the WFS protocol extension (and the right way to do it), but on everything else as well :-) As for the implementation of this thing, I'd say at first we're going to implement the extension in a postgis datastore "brother", and then try to move up the shareable stuff in an abstract class so that other JDBC based datastores can enjoy it as well. I've left file based datastores out intentionally, since to have decent performance I do need a database in the backend anyways. Possibly in a few days I'll ask for a new module on trunk in order to start coding the datastore. Cheers Andrea Aime ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
