From 9e5b55dfa23f6df445d07a6c5fa3ef574944311e Mon Sep 17 00:00:00 2001 From: Stein Magnus Jodal Date: Thu, 15 May 2014 00:20:11 +0200 Subject: [PATCH] docs: Update changelog --- docs/changelog.rst | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/docs/changelog.rst b/docs/changelog.rst index 43f73945..eac70a29 100644 --- a/docs/changelog.rst +++ b/docs/changelog.rst @@ -10,6 +10,12 @@ v0.19.0 (UNRELEASED) Feature release. +**Dependencies** + +- Mopidy now requires Tornado >= 3.1. + +- Mopidy no longer require CherryPy or ws4py for the HTTP frontend to work. + **Backend API** - Imports of the backend API from :mod:`mopidy.backends` no longer works. The @@ -35,6 +41,27 @@ Feature release. **HTTP frontend** +- CherryPy and ws4py have been replaced with Tornado. This will hopefully + reduce CPU usage on OS X (:issue:`445`) and improve error handling in corner + cases, like when returning the computer running Mopidy from suspend + (:issue:`718`). + +- Added support for installing web clients as Mopidy extensions. (Fixes: + :issue:`440`) (TODO: Link to relevant docs) + +- Added support for extending the HTTP frontend with additional server side + functionality. (TODO: Link to relevant docs) + +- Exposed the core API using HTTP POST requests with JSON-RPC payloads at + ``/mopidy/rpc``. This is the same JSON-RPC interface as is exposed over the + WebSocket at ``/mopidy/ws``, so you can run any core API command. + + The HTTP POST interfaces does not give you access to events from Mopidy, like + the WebSocket does. The WebSocket interface is still recommended for web + clients. The HTTP POST interface may be easier to use for simpler programs, + that just needs to query the currently playing track or similar. (TODO: Link + to relevant docs) + - If Zeroconf is enabled, we now announce the ``_mopidy-http._tcp`` service in addition to ``_http._tcp``. This is to make it easier to automatically find Mopidy's HTTP server among other Zeroconf-published HTTP servers on the