This is semi implementation specific, however, it would be good to make sure everyone does this the same way. The problems comes from having multiple versions of an object. Say you have 10 versions of an object and the server limits you to only 8 objects at a time. If you do a filter for added_after or no filter at all, you can run in to a situation where the x-headers coming back might have the same date, depending on how you interpret the specification. This will cause an automated client to get the same content over and over and over.
So while some systems will implement this differently and may not see this problem, others may. It would be good to add clarifying text to make sure clients do not get in to this situation.
This is semi implementation specific, however, it would be good to make sure everyone does this the same way. The problems comes from having multiple versions of an object. Say you have 10 versions of an object and the server limits you to only 8 objects at a time. If you do a filter for added_after or no filter at all, you can run in to a situation where the x-headers coming back might have the same date, depending on how you interpret the specification. This will cause an automated client to get the same content over and over and over.
So while some systems will implement this differently and may not see this problem, others may. It would be good to add clarifying text to make sure clients do not get in to this situation.