mopidy/mopidy — pull request #235 by jodal (2012-11-10 20:18:05+00:00)
Title: HTTP/WebSocket frontend

This is work in progress, and will surely not land in Mopidy 0.9.

After tweeting with @sergioeclectico a couple of days ago about how to get CherryPy running as a Mopidy frontend, I continued working on my proof of concept, and suddenly it had both WebSocket support and can host static files for a web client as well. Yay :-)

Still is still in an early stage, but I'm open for feedback/comments/requests from anyone, especially those making or thinking about making web clients for Mopidy. What do you want from a HTTP/WebSocket frontend in Mopidy? What does your dream API for making a web based music player look like?

@woutervanwijk This doesn't have Socket.IO support like your frontend prototype got (see #164), just a raw WebSocket. Would that block you from considering to use this frontend implementation for your client in the future? I'll make sure to read through your notes in the [woutervanwijk/mopidybrowserclient](https://github.com/woutervanwijk/mopidybrowserclient/blob/master/draft%20protocol%20and%20needs.txt) repo and have them in mind when planning the rest of the API, and I'm also open to requests/suggestions/pull requests.