2 .\" Copyright (C) 2004, 2005, 2006 Richard Kettlewell
4 .\" This program is free software; you can redistribute it and/or modify
5 .\" it under the terms of the GNU General Public License as published by
6 .\" the Free Software Foundation; either version 2 of the License, or
7 .\" (at your option) any later version.
9 .\" This program is distributed in the hope that it will be useful, but
10 .\" WITHOUT ANY WARRANTY; without even the implied warranty of
11 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
12 .\" General Public License for more details.
14 .\" You should have received a copy of the GNU General Public License
15 .\" along with this program; if not, write to the Free Software
16 .\" Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
19 .TH disorder_protocol 5
21 disorder_protocol \- DisOrder communication protocol
23 The DisOrder client and server communicate via the protocol described
26 The protocol is liable to change without notice. You are recommended to check
27 the implementation before believing this document.
29 Everything is encoded using UTF-8.
31 Commands and responses consist of a line followed (depending on the
32 command or response) by a message.
34 The line syntax is the same as described in \fBdisorder_config\fR(5) except
35 that comments are prohibited.
37 Bodies borrow their syntax from RFC821; they consist of zero or more ordinary
38 lines, with any initial full stop doubled up, and are terminated by a line
39 consisting of a full stop and a line feed.
41 Commands always have a command name as the first field of the line; responses
42 always have a 3-digit response code as the first field. See below for more
43 details about this field.
45 All commands require the connection to have been already authenticated unless
48 Neither commands nor responses have a body unless stated otherwise.
50 .B allfiles \fIDIRECTORY\fR [\fIREGEXP\fR]
51 Lists all the files and directories in \fIDIRECTORY\fR in a response body.
52 If \fIREGEXP\fR is present only matching files and directories are returned.
55 Instructs the server to treat the connection as if \fIUSER\fR had
56 authenticated it. Only trusted users may issue this command.
58 .B dirs \fIDIRECTORY\fR [\fIREGEXP\fR]
59 Lists all the directories in \fIDIRECTORY\fR in a response body.
60 If \fIREGEXP\fR is present only matching directories are returned.
62 .B disable \fR[\fBnow\fR]
63 Disables further playing. If the optional \fBnow\fR argument is present then
64 the current track is stopped.
67 Re-enables further playing, and is the opposite of \fBdisable\fR.
70 Reports whether playing is enabled. The second field of the response line will
71 be \fByes\fR or \fBno\fR.
74 Reports whether the named track exists. The second field of the response line
75 will be \fByes\fR or \fBno\fR.
77 .B files \fIDIRECTORY\fR [\fIREGEXP\fR]
78 Lists all the files in \fIDIRECTORY\fR in a response body.
79 If \fIREGEXP\fR is present only matching files are returned.
81 .B get \fITRACK\fR \fIPREF\fR
82 Gets a preference value. On success the second field of the response line will
85 .B get-global \fIKEY\fR
86 Get a global preference.
89 Gets the length of the track in seconds. On success the second field of the
90 response line will have the value.
93 Sends event log messages in a response body. The command will only terminate (and
94 close the response body with a final dot) when a further command is readable on
95 the control connection.
97 See \fBEVENT LOG\fR below for more details.
99 .B move \fITRACK\fR \fIDELTA\fR
100 Move a track in the queue. The track may be identified by ID (preferred) or
101 name (which might cause confusion if it's there twice). \fIDELTA\fR should be
102 an negative or positive integer and indicates how many steps towards the head
103 of the queue the track should be moved.
105 .B moveafter \fITARGET\fR \fIID\fR ...
106 Move all the tracks in the \fIID\fR list after ID \fITARGET\fR. If
107 \fITARGET\fR is the empty string then the listed tracks are put at the head of
108 the queue. If \fITARGET\fR is listed in the ID list then the tracks are moved
109 to just after the first non-listed track before it, or to the head if there is
112 .B part \fITRACK\fR \fICONTEXT\fI \fIPART\fR
113 Get a track name part. Returns an empty string if a name part cannot be
130 Pause the current track.
133 Add a track to the queue.
136 Reports what track is playing.
138 If the response is \fB252\fR then the rest of the response line consists of
139 track information (see below).
141 If the response is \fB259\fR then nothing is playing.
144 Sends back the preferences for \fITRACK\fR in a response body.
145 Each line of the response has the usual line syntax, the first field being the
146 name of the pref and the second the value.
149 Sends back the current queue in a response body, one track to a line, the track
150 at the head of the queue (i.e. next to be be played) first. See below for the
151 track information syntax.
154 Disable random play (but don't stop the current track).
160 Reports whether random play is enabled. The second field of the response line
161 will be \fByes\fR or \fBno\fR.
164 Sends back the current recently-played list in a response body, one track to a
165 line, the track most recently played last. See below for the track
169 Request that DisOrder reconfigure itself. Only trusted users may issue this
173 Remove the track identified by \fIID\fR. If \fBrestrict remove\fR is enabled
174 in the server's configuration then only the user that submitted the track may
178 Rescan all roots for new or obsolete tracks.
180 .B resolve \fITRACK\fR
181 Resolve a track name, i.e. if this is an alias then return the real track name.
184 Resume the current track after a \fBpause\fR command.
186 .B scratch \fR[\fIID\fR]
187 Remove the track identified by \fIID\fR, or the currently playing track if no
188 \fIID\fR is specified. If \fBrestrict scratch\fR is enabled in the server's
189 configuration then only the user that submitted the track may scratch it.
191 .B search \fITERMS\fR
192 Search for tracks matching the search terms. The results are put in a response
195 The search string is split in the usual way, with quoting supported, into a
196 list of terms. Only tracks matching all terms are included in the results.
198 Any terms of the form \fBtag:\fITAG\fR limits the search to tracks with that
201 All other terms are interpreted as individual words which must be present in
204 Spaces in terms don't currently make sense, but may one day be interpreted to
205 allow searching for phrases.
207 .B \fBset\fR \fITRACK\fR \fIPREF\fR \fIVALUE\fR
210 .B set-global \fIKEY\fR \fIVALUE\fR
211 Set a global preference.
214 Send server statistics in plain text in a response body.
217 Send the list of currently known tags in a response body.
219 .B \fBunset\fR \fITRACK\fR \fIPREF\fR
222 .B \fBunset-global\fR \fIKEY\fR
223 Unset a global preference.
225 .B user \fIUSER\fR \fIRESPONSE\fR
226 Authenticate as \fIUSER\fR.
228 When a connection is made the server sends a \fB221\fR response before any
229 command is received. As its first field this contains a challenge string
232 The \fIRESPONSE\fR consists of the SHA-1 hash of the user's password
233 concatenated with the challenge, encoded in hex.
236 Send back a response with the server version as the second field.
238 .B volume \fR[\fILEFT\fR [\fIRIGHT\fR]]
239 Get or set the volume.
241 With zero parameters just gets the volume and reports the left and right sides
242 as the 2nd and 3rd fields of the response.
244 With one parameter sets both sides to the same value. With two parameters sets
245 each side independently.
247 Responses are three-digit codes. The first digit distinguishes errors from
256 The second digit breaks down the origin of the response:
259 Generic responses not specific to the handling of the command. Mostly this is
263 Authentication responses.
266 Responses specific to the handling of the command.
268 The third digit provides extra information about the response:
271 Text part is just commentary.
274 Text part is a constant result e.g. \fBversion\fR.
277 Text part is a potentially variable result.
280 Text part is just commentary; a dot-stuffed body follows.
283 Text part is just commentary; an indefinite dot-stuffed body follows. (Used
287 Text part is just commentary; an indefinite dot-stuffed body follows. (Used
291 The text part is just commentary (but would normally be a response for this
292 command) e.g. \fBplaying\fR.
294 The server starts by issuing a challenge line, with response code 231. This
295 contains a random challenge encoded in hex.
297 The client should send back a \fBuser\fR command with username and a
298 hex-encoded response. The response is the SHA-1 hash of the user's password
300 .SH "TRACK INFORMATION"
301 Track information is encoded in a line (i.e. using the usual line syntax) as
302 pairs of fields. The first is a name, the second a value. The names have the
306 The time the track is expected to be played at.
309 A string uniquely identifying this queue entry.
312 The time the track was played at.
315 The user that scratched the track.
318 The current track state. Valid states are:
322 The player failed (exited with nonzero status but wasn't scratched).
325 The track is actually a scratch.
328 No player could be found for the track.
331 The track was played without any problems.
334 The track was scratched.
337 The track is currently playing.
340 In the queue, hasn't been played yet.
343 The track was terminated because the server is shutting down.
347 The user that submitted the track.
350 The filename of the track.
353 The time the track was added to the queue.
356 The wait status of the player in decimal.
358 Times are decimal integers using the server's \fBtime_t\fR.
360 For file listings, the regexp applies to the basename of the returned file, not
361 the whole filename, and letter case is ignored. \fBpcrepattern\fR(3) describes
364 Filenames are in UTF-8 even if the collection they come from uses some other
365 encoding - if you want to access the real file (in such cases as the filenames
366 actually correspond to a real file) you'll have to convert to whatever the
369 The event log consists of lines starting with a hexadecimal timestamp and a
370 keyword followed by (optionally) parameters. The parameters are quoted in the
371 usual DisOrder way. Currently the following keywords are used:
373 .B completed \fITRACK\fR
374 Completed playing \fITRACK\fR
376 .B failed \fITRACK\fR \fIERROR\fR
377 Completed playing \fITRACK\fR with an error status
380 User \fIUSER\fR moved some track(s). Further details aren't included any
383 .B playing \fITRACK\fR [\fIUSER\fR]
384 Started playing \fITRACK\fR.
386 .B queue \fIQUEUE-ENTRY\fR...
387 Added \fITRACK\fR to the queue.
389 .B recent_added \fIQUEUE-ENTRY\fR...
390 Added \fIID\fR to the recently played list.
392 .B recent_removed \fIID\fR
393 Removed \fIID\fR from the recently played list.
395 .B removed \fIID\fR [\fIUSER\fR]
396 Queue entry \fIID\fR was removed. This is used both for explicit removal (when
397 \fIUSER\fR is present) and when playing a track (when it is absent).
399 .B scratched \fITRACK\fR \fIUSER\fR
400 \fITRACK\fR was scratched by \fIUSER\fR.
402 .B state \fIKEYWORD\fR
403 Some state change occurred. The current set of keywords is:
407 Playing was disabled.
410 Random play was disabled.
416 Random play was enabled.
419 The current track was paused.
422 The current track was resumed.
425 .B volume \fILEFT\fR \fIRIGHT\fR
430 .B "TRACK INFORMATION"
437 \fBdisorder_config\fR(5),
~mdw / disorder / blob