James M Snell wrote:
Right now, the subscription feed uses "previous" to point to the archive feeds. Perhaps a better approach would be to to have an "archive" link relation that points to the first of a distinct set of archive feeds.
If I have to add yet another algorithm for paging support in addition to the ones that are already there, I'd be inclined to just dump the whole thing.
Yes, the paging in APP is a problem (one I've been largely ignoring up to this point in our own implementation). There is no way of reliably and efficiently reconstructing the entire feed history.
I would have thought a combination of RFC3229/feed with paging would be adequate. Something like that should work perfectly well with any client that already supports those features. It doesn't require the invention of a whole new system.
Regards James