Loading Profile...
COM Interface for developers
Much like iTunes, it would be excellent to have a way to interface with Spotify on a COM level. This would allow developers to very easily create such applications as remote controls (from mobile devices or other computers).
:)
:)
I’m excited
7
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I agree that an interface like this would be good, although COM isn't necessarily the best way of implementing this. A more platform-independent implementation would be for the application to have a built-in webserver which exposes web services (either SOAP or REST based) allowing control of Spotify by trusted applications. -
Inappropriate?I totally agree Steven, I just thought it would be easier (and more likely) to see it implemented as COM. I'm glad to see that no shortcuts are taken with regards to the coding of Spotify.
Many thanks :)
I’m thankful
-
Inappropriate?Com interface would be good, but that platform is a bit obsolute in the .NET days. Better with a core .NET/Mono dll library so we easy could start to make our own Spotify based solution with Visual C# express, Sharpdevelop or smiliar
I’m thankful
1 Comment
Add a comment
This is one of the best points
-
Eeeek! No... .NET is a very bad idea. It's such a slow and bulkey language, which requires .NET frameworks to be installed, it prevents any kind of portability to other operating systems. An HTTP interface would be a much better solution still, from COM.
I have a real problem with .NET, it's just not a well built infrastructure. -
Inappropriate?Com interface would be good, but that platform is a bit obsolute in the .NET days. Better with a core .NET/Mono dll library so we easy could start to make our own Spotify based solution with Visual C# express, Sharpdevelop or smiliar
I’m thankful
-
Inappropriate?Here's an open source re-implementation of libspotify that's cross platform.
http://github.com/noahwilliamsson/ope...
It builds on Windows and the Visual Studio project has targets for building libopenspotify as both a static library aswell as a dynamic library (DLL).
Unfortunately it's unmanaged code and I don't have much experience with COM and interfaces. If you can provide code that wraps up the exposed API as an interface or COM-object, please let me know. -
Inappropriate?I expect other developers with a decent amount of experience agree COM is the way forward. It does everything we need, it's well understood, used and supported (also still good for legacy apps and apps with custom scripting languages).
To those suggesting an in-built web server, let me propose another view: the last thing we need is yet another application providing its own dodgy web-interface when it's not being accessed *over the web*. We don't need the bloat (it's virtually guaranteed to be less efficient than a proper local IPC system), we don't need yet another udp or tcp port taken up and we don't need yet another trivially target-able avenue for exploits (even if it only binds to localhost). I wouldn't mind this being an optional system - e.g. some preference to "Enable local web interface" or such, but it should not be on by default and should probably require SSL and authentication too. (Hint: dodgy javascript, firefox bugs, IE bugs etc. can be exploited to attack "local" web servers.)
Regarding .NET: it makes interaction difficult from any other development environment than Visual Studio and, frankly, .NET's IPC is dodgy at best. The concept was fine, the implementation was shockingly bad. Things are better if (and only if) your target application was made for .NET 2.0 and later - and thats still flaky. Also, keep in mind users will then be forced to have the .NET Framework for applications to use use the interface (or at least some of the redist dlls) - sometimes this is simply not an option. Or does Spotify require .NET?
