@peterr wrote:
My only question is if you are changing the database access whether the polishing of playlist html and its javascript will hold up to your planned changes without requiring a simple change in access method. Let me look over the playlist.js and html code before I commit.
The changes won’t impact the xml methods available from javascript. The same methods will continue to work (creating, modifying, searching, retrieving file details, etc).
I do plenty of simple perl cgi mixed with Ajax, HTML and CSS for web based applications. Examples are available at the forementioned website, http://www.makehell.com, including a cgi I did last year for switching libraries under mt-daapd though a web interface (This was written to segregate lectures and novels from music) – it just swaps out config files and restarts mt-daapd. This is why, reconnection times are important to me.
There isn’t any perl, obviously, as the web part is handled by the server, but everything interesting including querying server status, updating configuration, accessing the database, etc, is all available from restful urls that return xml data sets.
The old way (iTunes-ish way) is here: http://trac.fireflymediaserver.org/wiki/XmlApi
Config updating is here:
http://trac.fireflymediaserver.org/wiki/xmlrpc
And there is more xml stuff available (faster) from the rsp module, but I don’t have that documented yet.
— Ron