Joe Gregorio wrote:
> 1. Override - Claim that in the context of the APP
> atom:updated MUST be updated for every change to an Entry, no
> leeway for 'significant' or 'insignificant'.
-0.5 (and only in the context of listing, the atom:updated would be the
"public value" when retrieving the Entry Resource, otherwise -1)
> 2. Obscure - Create a new element app:updated that acts the way we want
> and leave atom:updated as a client editable value.
+1 if it's called app:modified (it seems that it's something I already
seen on the list... I might have proposed it myself...)
> 3. Obscurer - Claim that the entries are ordered by an 'updated' property
> that has no representation in the Atom entry, think of it like the
> modified file time. The entries are ordered by this property, but you
> can't inspect or modify it.
-1
If I modify entry E1, then E2 on one station; then E1 and E2 again on
another station. When syncing from the first station, how will I know E1
and E2 have been modified again?
> 4. Ignore - Use atom:updated as specified and acknowledge
> that the client won't be able to synchronize with
> 'insignificant' updates, but only against 'significant' updates.
-1
Needed for offline editing, where a "GET before edit" is not possible.
Syncing must be "complete".
> We need to resolve the above question, but note that only
> if we select option #3 do we absolutely *need* {daterange}
> queries.
No strong opinion yet on {daterange}...
With {daterange} I could start crawling from the point I last sync'ed then
go forwards to the most recently modified entry. That way, even if someone
edits an entry while I'm syncing, I'll see it in the last chunk. This is
at least be what I would do if it were possible... {daterange} might
effectively be useless (or at least less usefull) when crawling backwards
to the past.
Without {daterange}, I must start at index 1 and go backwards until I find
an entry with app:modified earlier than when I last sync'ed. To be sure I
get the latest entries, I'll made a new request for 1-2, just in case
someone has edited an entry while I was syncing.
--
Thomas Broyer
