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
I have been using SpotifyAPI.Net (V5) for over 7 years in my ASP.Net project for my home entertainment system. I have been using it for all track/album/artist/playlist navigation, but until recently not for queuing and playing. There was at that time no Player web API, so I wrapped libspotify instead, even though that API was (even then) deprecated - there was no alternative available. Well, Spotify have finally pulled the plug on libspotity, and the Player web API is now available and working. So I have had to migrate to use that.
BUT ... I have (for now) stuck with V5.1.1 and largely synchronously, with locks in all of my SpotifyAPI.Net-calling methods. This is (as expected) giving poor responsiveness. So I know I need to migrate to v6 and async calls.
When I do so, will I need any locking at all on API calls? Are all the methods now re-entrant? I couldn't find any discussion on the topic in the docs or forum. But my code will be called (quite actively) from multiple threads and re-entrancy will definitely be an issue.
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
-
I have been using SpotifyAPI.Net (V5) for over 7 years in my ASP.Net project for my home entertainment system. I have been using it for all track/album/artist/playlist navigation, but until recently not for queuing and playing. There was at that time no Player web API, so I wrapped libspotify instead, even though that API was (even then) deprecated - there was no alternative available. Well, Spotify have finally pulled the plug on libspotity, and the Player web API is now available and working. So I have had to migrate to use that.
BUT ... I have (for now) stuck with V5.1.1 and largely synchronously, with locks in all of my SpotifyAPI.Net-calling methods. This is (as expected) giving poor responsiveness. So I know I need to migrate to v6 and async calls.
When I do so, will I need any locking at all on API calls? Are all the methods now re-entrant? I couldn't find any discussion on the topic in the docs or forum. But my code will be called (quite actively) from multiple threads and re-entrancy will definitely be an issue.
Beta Was this translation helpful? Give feedback.
All reactions