2006/3/23, James M Snell <[EMAIL PROTECTED]>: > > Switching to a full-feed response is a very easy thing to do. In all > honesty, I'm really not interested in inventing a way of sync'ing that > only works with our implementation... and I knew full well going in that > what we're doing currently with If-Modified-Since would be controversial > and would raise these types of questions... so with that, what is the > right approach? Right == a common way we can all do this so that it > works consistently across APP implementations? It doesn't have to be in > the core spec, an extension is fine.
I believe using app:modified ordering instead of atom:updated *is* the way to go as the Simplest Thing That Could Possibly Work. In the worst case, the client will get (page-size - 1) entries it does not need. On the advantage side, this would probably need to go into the core spec so will be widely used. On the drawback side, some clients might signal "updated" entries that have just be "modified" when the feed is also "subscribable" (i.e. not used only on the editing side but also as a publish mean). If you want to reduce the amount of information transitting over the network, then use RFC3229/feed, but the feed should (not must!) still be sorted by app:modified. -- Thomas Broyer
