My original message referred to a standard ordering. By that I was referring to APP Draft 14, section 10 "The Entries in the returned Atom Feed SHOULD be ordered by their "atom:updated" property, with the most recently updated Entries coming first in the document order."
We have large feeds so we implemented paging according to section 10.1 of APP draft 14. Assuming I've interpreted the APP draft correctly, we should be sending paged feeds where the entries are ordered by atom:updated. However we have certain clients that would like to see the feed entries ordered differently (app:edited for example). If this were sorted client side, the client would have to request every page in the feed and sort the large number of entries. If the client could request the feed sorted properly to begin with, then the client could stop paging when app:edited reached the timestamp of the last request. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James M Snell Sent: Thursday, May 24, 2007 12:06 AM To: [email protected] Subject: Re: Order of Entries within a Feed Ok, I hadn't read the message that started this thread so I missed that. Thanks for making that clear. - James A. Pagaltzis wrote: > * James M Snell <[EMAIL PROTECTED]> [2007-05-24 04:15]: >> The most reliable approach here would be to create an extension >> that allows the appropriate order to be recreated. > > My reading of Matthew Becker's request is that he isn't looking > for a way to sort the entries of a feed into a given order, > rather he wants to be able to make assumptions about the order > the entries appear in the feed, in order to optimise processing > in some way. That doesn't leave room for sorting after the fact; > either the entries are in the right order for the optimisation to > hold, or they're not. > > Regards,
