Andrea Aime wrote: > Forgot this one... man, your feedback was quite big :-p Heh - and this was the only idea I thought was actually good. >> GetDiff - GetTransaction Request option >> It would be *nice* if the result was *not* a GetFeatures extensions >> but instead the exact Transaction request documented required to make >> the change; no messing around or inventing new xml schema is requried >> here. > My take on this is that no client has the infrastructure in place to > parse a Transaction request, they only have generating code (which > may well be just a string catenation)... Don't follow you about generating code? The Transaction format is quite clear though - broken down into delete, update, add ... think this one is perfect. If you want to talk further I suggest we make a real example and work through both approaches; and then probably write an example parser (are you targeting a Java application programmer or AJAX here?) > We could have multiple output format for diff, and > "rollback-transaction" could be one created just for the sake of doing > rollback with a diff + transation, but... see my next comment Don't bother; let's figure out the right thing and do it... >> This is consistent with Galdos cascading WFS-T approach and would be >> a *great* benefit for keeping servers in sync. >> (Please consider this idea). > I don't follow you... why Galdos matters in a GetDiff request? Because they have covered this territory before us; and thus we can say the idea is implementable - and better yet deployed. >> Rollback - don't do it, use GetDiff > I disagree here for two reasons: > * doing a rollback in the server is very quick, it's just a matter of > a couple of queries (much faster, the more the bigger you revert is) Ah you putting your performance concerns before the design; I had hoped not to introduce any more concepts for users to concern themselves with. Having operations that slot together etc... > * if the rollback is big, the transaction request to do the actual > work can be a huge gml document. Like this point; at least *define* the service in terms of being exactly the same as getting the difference and applying it using transaction (makes the description very clear).
Cheers, Jody ------------------------------------------------------------------------- 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
