andpp/mopidy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: Minor JSON-RPC doc improvements

Browse Source
This commit is contained in:
Stein Magnus Jodal 2014-05-15 21:35:06 +02:00
parent 7b6735b9af
commit e2bec6aa06
1 changed files with 33 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

51
docs/api/http.rst
View File

@ -25,33 +25,32 @@ WebSocket API for use both from browsers and Node.js.
stable. stable.
.. _http-post-api:
HTTP POST API
=============
TODO
.. _websocket-api: .. _websocket-api:
WebSocket API WebSocket API
============= =============
The web server exposes a WebSocket at ``/mopidy/ws/``. The WebSocket gives you The Mopidy web server exposes a WebSocket at http://localhost:6680/mopidy/ws,
access to Mopidy's full API and enables Mopidy to instantly push events to the where the ``localhost:6680`` part will vary with your local setup. The
client, as they happen. WebSocket gives you access to Mopidy's full API and enables Mopidy to instantly
push events to the client, as they happen.
On the WebSocket we send two different kind of messages: The client can send On the WebSocket we send two different kind of messages: The client can send
JSON-RPC 2.0 requests, and the server will respond with JSON-RPC 2.0 responses. :ref:`JSON-RPC 2.0 requests <json-rpc>`, and the server will respond with
In addition, the server will send event messages when something happens on the JSON-RPC 2.0 responses. In addition, the server will send :ref:`event messages
server. Both message types are encoded as JSON objects. <json-events>` when something happens on the server. Both message types are
encoded as JSON objects.
Event messages .. _json-rpc:
==============
Event objects will always have a key named ``event`` whose value is the event
type. Depending on the event type, the event may include additional fields for
related data. The events maps directly to the :class:`mopidy.core.CoreListener`
API. Refer to the ``CoreListener`` method names is the available event types.
The ``CoreListener`` method's keyword arguments are all included as extra
fields on the event objects. Example event message::
{"event": "track_playback_started", "track": {...}}
JSON-RPC 2.0 messaging JSON-RPC 2.0 messaging
====================== ======================
@ -81,3 +80,19 @@ Example JSON-RPC response::
The JSON-RPC method ``core.describe`` returns a data structure describing all The JSON-RPC method ``core.describe`` returns a data structure describing all
available methods. If you're unsure how the core API maps to JSON-RPC, having a available methods. If you're unsure how the core API maps to JSON-RPC, having a
look at the ``core.describe`` response can be helpful. look at the ``core.describe`` response can be helpful.
.. _json-events:
Event messages
==============
Event objects will always have a key named ``event`` whose value is the event
type. Depending on the event type, the event may include additional fields for
related data. The events maps directly to the :class:`mopidy.core.CoreListener`
API. Refer to the :class:`~mopidy.core.CoreListener` method names is the
available event types. The :class:`~mopidy.core.CoreListener` method's keyword
arguments are all included as extra fields on the event objects. Example event
message::
{"event": "track_playback_started", "track": {...}}