On 7/11/05 2:49 AM, "James M Snell" <[EMAIL PROTECTED]> wrote:
>>> http://example.org/entries?b={begin}&e={end} > 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. That should work then -- the APP-client needs to remember the date of it's last sync and then go retrieve the entire listing feed to sync up. This works because the listing feed is bounded by the dates, and thus the APP-client knows when to stop paging. It wouldn't work the collection feed though because it wouldn't know when to stop paging. e.
