manwithaplan wrote:Very interesting, much appreciate the work here. Couple questions if I were to venture toward a FireTV...
A. Does your code support the use of SSL for the Subsonic access? Many of us of course would NEVER run Subsonic on straight HTTP, but instead HTTPS with real certificates that we purchase from real CA's, etc.
B. Does your code support Subsonic 5.2, that literally hit the street 2 days ago? If not, when do you estimate it will?
Thanks again! These are interesting capabilities for sure.
A. There is nothing *I* know of that is stopping connecting to an SSL server. However, I don't have one nor the time or patience to set one up. Everything I have read says that CORS should work without any issues when an HTTP client talks to an HTTPS server, and Adobe's website says that phonegap apps shouldn't care either way what they talk to, aside from certificate signatures.
I do know from reading a bit that Chrome does not like talking to a self-signed cert that doesn't have a CA behind it, without you adding the cert directly to Chrome's cert store on your desktop. When it happens in a CORS situation, the browser doesn't prompt to ask if you want to make an exception the way it does with self-signed certs in other contexts. This would impact using Chrome for the web version of the player as well as the Chrome app in the web-store (which is the same thing).
If it does not work, please let me know because I really don't know why it shouldn't. You can try the web version (
http://p.subfireplayer.net/ ) first before downloading the Fire app to test and verify. It is only using just the html5 audio tag and basic REST calls, so I can only do what the browsers let me do.
B. There is nothing existing that is changed as far as the API goes between 5.1 to 5.2. 5.2 only adds new features like the play queue which I do intend to take advantage of at some point, but I'm still working on the 'browse' mode (viewing folders and playing albums directly rather than shuffled from the top level). The 5.0 requirement was only because of a bug that 4.9 had in its headers for CORS support. While it takes advantage of 5.1 features (things like playlist cover art), if they aren't there the client continues to work properly in every other regard.
I certainly intend to add ID3 support and will take advantage of 5.2's new features in that capacity when I get there, but that's probably still a few months away.
Posted: Wed May 21, 2014 11:07 pm
), with hopes that i can test it and get it submitted for the Amazon app store by the end of the month. No idea how long the review process is after that, of course. We'll see.