I agree with you hypothetically. But my question was about their real world issues.
They could, in theory, have ids for songs-in-playlists. But they don't in fact have them and their RPC api doesn't require them. That's what I'm interested in. Not how they could change their architecture to make REST work.
Comments
I agree with you hypothetically. But my question was about their real world issues.
They could, in theory, have ids for songs-in-playlists. But they don't in fact have them and their RPC api doesn't require them. That's what I'm interested in. Not how they could change their architecture to make REST work.
if it's a big deal to make that change then their underlying architecture needs a review.