From 4562de56157288fb62654e83f532adbcf445d999 Mon Sep 17 00:00:00 2001 From: Stein Magnus Jodal Date: Tue, 20 May 2014 21:11:30 +0200 Subject: [PATCH] docs: Add references to new API docs --- docs/api/http-server.rst | 2 ++ docs/changelog.rst | 6 +++--- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/api/http-server.rst b/docs/api/http-server.rst index 0f55d650..2d5b6a17 100644 --- a/docs/api/http-server.rst +++ b/docs/api/http-server.rst @@ -1,3 +1,5 @@ +.. _http-server-api: + ******************** HTTP server side API ******************** diff --git a/docs/changelog.rst b/docs/changelog.rst index 4377f39b..b10575ed 100644 --- a/docs/changelog.rst +++ b/docs/changelog.rst @@ -61,7 +61,7 @@ Feature release. :issue:`440`) (TODO: Link to relevant docs) - Added support for extending the HTTP frontend with additional server side - functionality. (TODO: Link to relevant docs) + functionality. See :ref:`http-server-api` for details. - 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 @@ -70,8 +70,8 @@ Feature release. 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) + that just needs to query the currently playing track or similar. See + :ref:`http-post-api` for details. - 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