I can't give a +1 but there is an existing geosync (no "h") module in community that is not being used anymore. You could always use that one :)
On 3/23/10 1:45 PM, Andrea Aime wrote: > Hi, > I would like to ask space for a new module in the community > area. > > The module will be called GeoSynch and will build on top of the > versioning work done in the past to allow a distributed network > of editors to share their work on a set of common layers. > It's by all intents and purposes a simplified down version of > a distributed versioning control system. > > Each editing node, that we call unit, will have one instance > of GeoServer running, a versioning PostGIS data store, and > one or more uDig clients directly connected to the PostGIS > data store via the versioning data store that will make edits > to it. > > A central node (called, in an explosion of creativity, Central) > will contact each unit in turn and trade changesets with them: > it will gather all of the new unit changes and push to the unit > all of the changes gathered from the other units since the > last synchronization. > Unlike standard VCS Central takes the control of the synch process, > this is done for two reasons: > - bandwitdh control: this way central can operate at maximum capacity > without being swamped > - concurrency control: to keep the design simple it's not possible > for two units to synchronize on the same layer at the same time. > Central will orchestrate the synchronizations so that the above > cannot happen. > > Since units can edit the same feauture at the same time, conflict > might happen: the system will take care of them, raising them > on the Unit side and allowing the uDig client to deal with them. > > The GeoSynch community module will implement the call and > synchronization parts of the above, and will be configured to > act either as Central or as a Unit. > > Oh, if you're wondering about the WFS-V protocol, there will > be no actual use of it as GeoSynch will build changesets talking > directly to the datastore, and the two GeoSynchs will talk to each > other using their own protocol. > However, it might be that we're going to reuse some bits of the WFS-V > XML encoding. > > While this work is sponsored for a specific purpose and > has a contract and deadlines behind it, we'll make sure that > the GeoSynch module stays of general interest and can > be used in other setups. In fact in the current design there > are no specific vendor bits [1] > > Sooo... can I get my community module? :-) > > Cheers > Andrea > > [1]: tomorrow I'll try to share a bit of of the design > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
