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 current GetItems Endpoint accepts a filter option, however it's an opt out by media type. This can lead to extra slow syncs when a user has two libraries of the same type, but only has one synced to Kodi. In the current implementation, we would receive updates for both libraries and have to sort through them locally.
In a perfect world, I'd also like to change the API response to have full items. Currently, we get a list of item IDs, but then in order to process them locally in Kodi we have to make a separate request back to the server for each item. It would be far more efficient if we could retrieve a list of all the updated items at one time. If we go this route, I think we should probably make a new endpoint that returns the full items instead of changing the existing one. Otherwise, it's going to be a pretty big change with potential to break some/most setups.
The text was updated successfully, but these errors were encountered:
Linked issue from the Kodi repo seems to indicate that the existing plugin logic is marking things as changed when we might not care about them. Probably should be it's own issue, but since it's all part of the same overall sync issues discussion it's worth mentioning here.
The current
GetItems
Endpoint accepts afilter
option, however it's an opt out by media type. This can lead to extra slow syncs when a user has two libraries of the same type, but only has one synced to Kodi. In the current implementation, we would receive updates for both libraries and have to sort through them locally.In a perfect world, I'd also like to change the API response to have full items. Currently, we get a list of item IDs, but then in order to process them locally in Kodi we have to make a separate request back to the server for each item. It would be far more efficient if we could retrieve a list of all the updated items at one time. If we go this route, I think we should probably make a new endpoint that returns the full items instead of changing the existing one. Otherwise, it's going to be a pretty big change with potential to break some/most setups.
The text was updated successfully, but these errors were encountered: