Re: [geogig-dev] Notes about import and sync operations from QGIS plugin

[Victor Olaya <volaya@xxxxxxxxxxxxxxxx>]

[DH] Victor, would this mean that mobile and other 3rd party apps would need to manage data in the same way? I'm not sure I'm comfortable pushing this responsibility to the clients. It seems we may end up introducing inconsistencies across clients for how sync works (due to differences in implementations) - and leading users to distrust sync.

no, other apps can do that in whatever fashion they want. But if you dont have a full repo locally, and a local geogig to manage that, i think that the current webapi doesnt have a way of doing a push which actually can signal conflicts, etc... If i am not wrong, with a mobile client (which wont have geogig installed), the client will have to find the conflicts itself, since there is no way of doing it otherwise (maybe there is, but i cannot figure it out by looking at the webapi docs...)

[DH] One item we haven't discussed much yet w.r.t. the versioning workflow, is the need to support a POST operation. This is the GIS workflow term for how a user merges changes from their version(branch) to another version(parent branch such as master). The behavior of POST is that the operation either successfully merges changes into the other branch (no conflicts) or the operation fails (conflicts). The user must fetch and resolve conflicts before retrying the POST on failure.

Well, that's what the operation i described does :-)

--

Victor Olaya

Software Engineer | Boundless
volaya@xxxxxxxxxxxxxxxx
@boundlessgeo