In my current impl, it operates on the last-modified date of the entry
file (entries are stored in the file system). This is equivalent to
app:modified but is not surfaced into the entry metadata. This date is
surfaced in the Last-Modified HTTP header when I GET or HEAD the
editable representation of the entry.
- James
Eric Scheid wrote:
On 6/11/05 1:45 PM, "James M Snell" <[EMAIL PROTECTED]> wrote:
The way I currently do this in my current experimental implementation is:
http://example.org/entries?b={begin}&e={end}
The resulting feed contains all entries that have been modified in the
specified timeframe. For the sync, I do a conditional GET on member
specifying if-modified-since to get the editable representation.
does {begin} and {end} operate on atom:updated or app:modified?
e.
