StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>One idea that is probably too simple is using the same method as SVN or CVS.</strong></p> <ol> <li>First, a device extracts the data (checkout). </li> <li>Upon sync, it would do update</li> <li>if you got any conflicts, ask the user which version it prefers (I'd give the options to choose one of the two, create a new one or consider them two different items)</li> <li>after solving conflicts, commit the current state</li> </ol> <p><strong>Things to think about:</strong></p> <ol> <li>each item should match to a file (better for complex data) or all items (belonging to the same user) should be placed in the same file?</li> <li>using item's id could make things easier to avoid false-conflicts between items with similar contents</li> <li>you probably should convert any item that you exchange to a xml file (or similar) so the versions can be tracked easier</li> <li>this doesn't mean that you need to send xml back and forth. You can convert xml to the format you wish (url encoded parameters to xml, for example)</li> <li>using a strict format for the files under revision control will make things easier to sync</li> </ol> <p><strong>Explaining my last point:</strong></p> <p>Don't encode url parameters in the order they arrive, but choose some logical order. For example, "a=111&b=222" and "b=222&a=111" should be stored with the same text. Be sure that the same data will always have the same representation even if you receive it in a different format.</p> <p>These were just my initial thoughts...</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload