You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The schema example shows that an authorization object can be included inside the link properties. Would it also be valid, or is there any plan, to include the progression object itself there?
The rationale is that a client browsing many books or chapters currently needs to call each progression endpoint individually to retrieve the current read state. Including the progression data directly in the feed would avoid those extra calls and make large libraries much more efficient.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hello gents,
I have a question about the newer OPDS progression schema.
Is the progression property inside the progression link currently supported, or is there any plan to support something like this?
The schema example shows that an authorization object can be included inside the link properties. Would it also be valid, or is there any plan, to include the progression object itself there?
The rationale is that a client browsing many books or chapters currently needs to call each progression endpoint individually to retrieve the current read state. Including the progression data directly in the feed would avoid those extra calls and make large libraries much more efficient.
All reactions