2 .\" Copyright (C) 2004-2008 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.
27 You are recommended to check the implementation before believing this document.
29 Everything is encoded using UTF-8.
31 .B "CHARACTER ENCODING"
32 below for more detail on character encoding issues.
34 Commands and responses consist of a line perhaps followed (depending on the
35 command or response) by a body.
37 The line syntax is the same as described in \fBdisorder_config\fR(5) except
38 that comments are prohibited.
40 Bodies borrow their syntax from RFC821; they consist of zero or more ordinary
41 lines, with any initial full stop doubled up, and are terminated by a line
42 consisting of a full stop and a line feed.
44 Commands always have a command name as the first field of the line; responses
45 always have a 3-digit response code as the first field.
46 See below for more details about this field.
48 All commands require the connection to have been already authenticated unless
50 If not stated otherwise, the \fBread\fR right is sufficient to execute
53 Neither commands nor responses have a body unless stated otherwise.
55 .B adduser \fIUSERNAME PASSWORD \fR[\fIRIGHTS\fR]
56 Create a new user with the given username and password.
57 The new user's rights list can be specified; if it is not
58 then the \fBdefault_rights\fR setting applies instead.
59 Requires the \fBadmin\fR right, and only works on local
62 .B allfiles \fIDIRECTORY\fR [\fIREGEXP\fR]
63 List all the files and directories in \fIDIRECTORY\fR in a response body.
64 If \fIREGEXP\fR is present only matching files and directories are returned.
66 .B confirm \fICONFIRMATION
67 Confirm user registration.
68 \fICONFIRMATION\fR is as returned from \fBregister\fR below.
69 This command can be used without logging in.
72 Log a user back in using a cookie created with \fBmake\-cookie\fR.
73 The response contains the username.
75 .B deluser \fIUSERNAME
76 Delete the named user.
77 Requires the \fBadmin\fR right, and only works on local connections.
79 .B dirs \fIDIRECTORY\fR [\fIREGEXP\fR]
80 List all the directories in \fIDIRECTORY\fR in a response body.
81 If \fIREGEXP\fR is present only matching directories are returned.
83 .B disable \fR[\fBnow\fR]
84 Disable further playing.
85 If the optional \fBnow\fR argument is present then the current track
87 Requires the \fBglobal prefs\fR right.
89 .B edituser \fIUSERNAME PROPERTY VALUE
91 With the \fBadmin\fR right any username and property may be specified.
92 Otherwise the \fBuserinfo\fR right is required and only the
93 \fBemail\fR and \fBpassword\fR properties may be set.
95 User properties are syntax-checked before setting. For instance \fBemail\fR
96 must contain an "@" sign or you will get an error. (Setting an empty value for
97 \fBemail\fR is allowed and removes the property.)
100 Re-enable further playing, and is the opposite of \fBdisable\fR.
101 Requires the \fBglobal prefs\fR right.
104 Report whether playing is enabled.
105 The second field of the response line will be \fByes\fR or \fBno\fR.
107 .B exists \fITRACK\fR
108 Report whether the named track exists.
109 The second field of the response line will be \fByes\fR or \fBno\fR.
111 .B files \fIDIRECTORY\fR [\fIREGEXP\fR]
112 List all the files in \fIDIRECTORY\fR in a response body.
113 If \fIREGEXP\fR is present only matching files are returned.
115 .B get \fITRACK\fR \fIPREF\fR
116 Getsa preference value.
117 On success the second field of the response line will have the value.
119 If the track or preference do not exist then the response code is 555.
121 .B get\-global \fIKEY\fR
122 Get a global preference.
124 If the preference does not exist then the response code is 555.
126 .B length \fITRACK\fR
127 Get the length of the track in seconds.
128 On success the second field of the response line will have the value.
131 Send event log messages in a response body.
132 The command will never terminate.
133 Any further data sent to the server will be discarded (explicitly;
134 i.e. it will not accumulate in a buffer somewhere).
136 See \fBEVENT LOG\fR below for more details.
139 Returns an opaque string that can be used by the \fBcookie\fR command to log
140 this user back in on another connection (until the cookie expires).
142 .B move \fITRACK\fR \fIDELTA\fR
143 Move a track in the queue.
144 The track may be identified by ID (preferred) or name (which might cause
145 confusion if it's there twice).
146 \fIDELTA\fR should be an negative or positive integer and indicates how
147 many steps towards the head of the queue the track should be moved.
149 Requires one of the \fBmove mine\fR, \fBmove random\fR or \fBmove any\fR rights
150 depending on how the track came to be added to the queue.
152 .B moveafter \fITARGET\fR \fIID\fR ...
153 Move all the tracks in the \fIID\fR list after ID \fITARGET\fR.
154 If \fITARGET\fR is the empty string then the listed tracks are put
155 at the head of the queue.
156 If \fITARGET\fR is listed in the ID list then the tracks are moved
157 to just after the first non-listed track before it, or to the head if there is
160 Requires one of the \fBmove mine\fR, \fBmove random\fR or \fBmove any\fR rights
161 depending on how the tracks came to be added to the queue.
163 .B new \fR[\fIMAX\fR]
164 Send the most recently added \fIMAX\fR tracks in a response body.
165 If the argument is ommitted, the \fBnew_max\fR most recent tracks are
166 listed (see \fBdisorder_config\fR(5)).
172 as a keepalive measure.
173 This command does not require authentication.
175 .B part \fITRACK\fR \fICONTEXT\fI \fIPART\fR
176 Get a track name part.
177 Returns an empty string if a name part cannot be constructed.
193 Pause the current track.
194 Requires the \fBpause\fR right.
197 Add a track to the queue.
198 The response contains the queue ID of the track.
199 Requires the \fBplay\fR right.
202 Report what track is playing.
204 If the response is \fB252\fR then the rest of the response line consists of
205 track information (see below).
207 If the response is \fB259\fR then nothing is playing.
210 Send back the preferences for \fITRACK\fR in a response body.
211 Each line of the response has the usual line syntax, the first field being the
212 name of the pref and the second the value.
215 Send back the current queue in a response body, one track to a line, the track
216 at the head of the queue (i.e. next to be be played) first.
217 See below for the track information syntax.
220 Disable random play (but don't stop the current track).
221 Requires the \fBglobal prefs\fR right.
225 Requires the \fBglobal prefs\fR right.
228 Report whether random play is enabled.
229 The second field of the response line will be \fByes\fR or \fBno\fR.
232 Send back the current recently-played list in a response body, one track to a
233 line, the track most recently played last.
234 See below for the track information syntax.
237 Request that DisOrder reconfigure itself.
238 Requires the \fBadmin\fR right.
240 .B register \fIUSERNAME PASSWORD EMAIL
242 Requires the \fBregister\fR right.
243 The result contains a confirmation string; the user will be be able
244 to log in until this has been presented back to the server via the
245 \fBconfirm\fR command.
247 .B reminder \fIUSERNAME\fR
248 Send a password reminder to user \fIUSERNAME\fR.
249 If the user has no valid email address, or no password, or a
250 reminder has been sent too recently, then no reminder will be sent.
253 Remove the track identified by \fIID\fR.
254 Requires one of the \fBremove mine\fR, \fBremove random\fR or
255 \fBremove any\fR rights depending on how the
256 track came to be added to the queue.
258 .B rescan \fR[\fBwait\fR] \fR[\fBfresh\fR]
259 Rescan all roots for new or obsolete tracks.
260 Requires the \fBrescan\fR right.
262 If the \fBwait\fR flag is present then the response is delayed until the rescan
264 Otherwise the response arrives immediately.
265 This is primarily intended for testing.
267 If the \fBfresh\fR flag is present a rescan is already underway then a second
268 rescan will be started when it completes.
269 The default behavior is to piggyback on the existing rescan.
271 NB that \fBfresh\fR is currently disabled in the server source, so using this
272 flag will just provoke an error.
274 .B resolve \fITRACK\fR
275 Resolve a track name, i.e. if this is an alias then return the real track name.
278 Resume the current track after a \fBpause\fR command.
279 Requires the \fBpause\fR right.
281 .B revoke \fBcookie\fR
282 Revoke a cookie previously created with \fBmake\-cookie\fR.
283 It will not be possible to use this cookie in the future.
286 Report the RTP broadcast (or multicast) address, in the form \fIADDRESS
288 This command does not require authentication.
290 .B scratch \fR[\fIID\fR]
291 Remove the track identified by \fIID\fR, or the currently playing track if no
292 \fIID\fR is specified.
293 Requires one of the \fBscratch mine\fR, \fBscratch random\fR or
294 \fBscratch any\fR rights depending on how the track came to be
297 .B search \fITERMS\fR
298 Search for tracks matching the search terms.
299 The results are put in a response body, one to a line.
301 The search string is split in the usual way, with quoting supported, into a
303 Only tracks matching all terms are included in the results.
305 Any terms of the form \fBtag:\fITAG\fR limits the search to tracks with that
308 All other terms are interpreted as individual words which must be present in
311 Spaces in terms don't currently make sense, but may one day be interpreted to
312 allow searching for phrases.
314 .B \fBset\fR \fITRACK\fR \fIPREF\fR \fIVALUE\fR
316 Requires the \fBprefs\fR right.
318 .B set\-global \fIKEY\fR \fIVALUE\fR
319 Set a global preference.
320 Requires the \fBglobal prefs\fR right.
323 Send server statistics in plain text in a response body.
326 Send the list of currently known tags in a response body.
328 .B \fBunset\fR \fITRACK\fR \fIPREF\fR
330 Requires the \fBprefs\fR right.
332 .B \fBunset\-global\fR \fIKEY\fR
333 Unset a global preference.
334 Requires the \fBglobal prefs\fR right.
336 .B user \fIUSERNAME\fR \fIRESPONSE\fR
337 Authenticate as user \fIUSERNAME\fR.
342 .B userinfo \fIUSERNAME PROPERTY
346 Send the list of currently known users in a response body.
349 Send back a response with the server version as the second field.
351 .B volume \fR[\fILEFT\fR [\fIRIGHT\fR]]
352 Get or set the volume.
354 With zero parameters just gets the volume and reports the left and right sides
355 as the 2nd and 3rd fields of the response.
357 With one parameter sets both sides to the same value.
358 With two parameters sets each side independently.
359 Setting the volume requires the \fBvolume\fR right.
361 Responses are three-digit codes.
362 The first digit distinguishes errors from succesful responses:
370 The second digit breaks down the origin of the response:
373 Generic responses not specific to the handling of the command.
374 Mostly this is parse errors.
377 51x errors indicate that the user had insufficient rights for the command.
380 Authentication responses.
383 Responses specific to the handling of the command.
385 The third digit provides extra information about the response:
388 Text part is just commentary.
391 Text part is a constant result e.g. \fBversion\fR.
394 Text part is a potentially variable result.
397 Text part is just commentary; a dot-stuffed body follows.
400 Text part is just commentary; an indefinite dot-stuffed body follows.
401 (Used for \fBlog\fR.)
404 Used with "normal" errors, for instance a preference not being found.
405 The text part is commentary.
408 The text part is just commentary (but would normally be a response for this
409 command) e.g. \fBplaying\fR.
411 Result strings (not bodies) intended for machine parsing (i.e. xx1 and xx2
412 responses) are quoted.
414 When a connection is made the server sends a \fB231\fR response before any
416 This contains a protocol generation, an algorithm name and a
417 challenge encoded in hex, all separated by whitespace.
419 The current protocol generation is \fB2\fR.
421 The possible algorithms are (currently) \fBsha1\fR, \fBsha256\fR, \fBsha384\fR
423 \fBSHA1\fR etc work as synonyms.
425 The \fBuser\fR response consists of the selected hash of the user's password
426 concatenated with the challenge, encoded in hex.
427 .SH "TRACK INFORMATION"
428 Track information is encoded in a line (i.e. using the usual line syntax) as
430 The first is a name, the second a value.
431 The names have the following meanings:
434 The time the track is expected to be played at.
437 A string uniquely identifying this queue entry.
440 The time the track was played at.
443 The user that scratched the track.
446 The current track state.
451 The player failed (exited with nonzero status but wasn't scratched).
454 The track is actually a scratch.
457 No player could be found for the track.
460 The track was played without any problems.
463 The track was scratched.
466 The track is currently playing.
469 In the queue, hasn't been played yet.
472 The track was terminated because the server is shutting down.
476 The user that submitted the track.
479 The filename of the track.
482 The time the track was added to the queue.
485 The wait status of the player in decimal.
487 Times are decimal integers using the server's \fBtime_t\fR.
489 For file listings, the regexp applies to the basename of the returned file, not
490 the whole filename, and letter case is ignored.
491 \fBpcrepattern\fR(3) describes the regexp syntax.
493 Filenames are in UTF-8 even if the collection they come from uses some other
494 encoding - if you want to access the real file (in such cases as the filenames
495 actually correspond to a real file) you'll have to convert to whatever the
498 The event log consists of lines starting with a hexadecimal timestamp and a
499 keyword followed by (optionally) parameters.
500 The parameters are quoted in the usual DisOrder way.
501 Currently the following keywords are used:
503 .B completed \fITRACK\fR
504 Completed playing \fITRACK\fR
506 .B failed \fITRACK\fR \fIERROR\fR
507 Completed playing \fITRACK\fR with an error status
509 .B moved \fIUSERNAME\fR
510 User \fIUSERNAME\fR moved some track(s).
511 Further details aren't included any more.
513 .B playing \fITRACK\fR [\fIUSERNAME\fR]
514 Started playing \fITRACK\fR.
516 .B queue \fIQUEUE-ENTRY\fR...
517 Added \fITRACK\fR to the queue.
519 .B recent_added \fIQUEUE-ENTRY\fR...
520 Added \fIID\fR to the recently played list.
522 .B recent_removed \fIID\fR
523 Removed \fIID\fR from the recently played list.
525 .B removed \fIID\fR [\fIUSERNAME\fR]
526 Queue entry \fIID\fR was removed.
527 This is used both for explicit removal (when \fIUSERNAME\fR is present)
528 and when playing a track (when it is absent).
533 .B scratched \fITRACK\fR \fIUSERNAME\fR
534 \fITRACK\fR was scratched by \fIUSERNAME\fR.
536 .B state \fIKEYWORD\fR
537 Some state change occurred.
538 The current set of keywords is:
542 The current track completed successfully.
545 Playing was disabled.
548 Random play was disabled.
554 Random play was enabled.
557 The current track failed.
560 The current track was paused.
563 A track started playing.
566 The current track was resumed.
569 The current track was scratched.
571 To simplify client implementation, \fBstate\fR commands reflecting the current
572 state are sent at the start of the log.
575 .B volume \fILEFT\fR \fIRIGHT\fR
580 .B "TRACK INFORMATION"
582 .SH "CHARACTER ENCODING"
583 All data sent by both server and client is encoded using UTF-8.
584 Moreover it must be valid UTF-8, i.e. non-minimal sequences are not
585 permitted, nor are surrogates, nor are code points outside the
588 There are no particular normalization requirements on either side of the
590 The server currently converts internally to NFC, the client must
591 normalize the responses returned if it needs some normalized form for further
594 The various characters which divide up lines may not be followed by combining
596 For instance all of the following are prohibited:
599 LINE FEED followed by a combining character.
600 For example the sequence LINE FEED, COMBINING GRAVE ACCENT is never permitted.
603 APOSTROPHE or QUOTATION MARK followed by a combining character when used to
605 For instance a line starting APOSTROPHE, COMBINING CEDILLA is prohibited.
607 Note that such sequences are not prohibited when the quote character cannot be
608 interpreted as a field delimiter.
609 For instance APOSTROPHE, REVERSE SOLIDUS, APOSTROPHE, COMBINING CEDILLA,
610 APOSTROPHE would be permitted.
613 REVERSE SOLIDUS (BACKSLASH) followed by a combining character in a quoted
614 string when it is the first character of an escape sequence.
615 For instance a line starting APOSTROPHE, REVERSE SOLIDUS, COMBINING TILDE
618 As above such sequences are not prohibited when the character is not being used
619 to start an escape sequence.
620 For instance APOSTROPHE, REVERSE SOLIDUS, REVERSE SOLIDS, COMBINING TILDE,
621 APOSTROPHE is permitted.
624 Any of the field-splitting whitespace characters followed by a combining
625 character when not part of a quoted field.
626 For instance a line starting COLON, SPACE, COMBINING CANDRABINDU is prohibited.
628 As above non-delimiter uses are fine.
631 The FULL STOP characters used to quote or delimit a body.
633 Furthermore none of these characters are permitted to appear in the context of
634 a canonical decomposition (i.e. they must still be present when converted to
636 In practice however this is not an issue in Unicode 5.0.
638 These rules are consistent with the observation that the split() function is
639 essentially a naive ASCII parser.
640 The implication is not that these sequences never actually appear in
641 the protocol, merely that the server is not required to honor them in
642 any useful way nor be consistent between versions: in current
643 versions the result will be lines and fields that start with combining
644 characters and are not necessarily split where you expect, but future versions
645 may remove them, reject them or ignore some or all of the delimiters that have
646 following combining characters, and no notice will be given of any change.
652 \fBdisorder_config\fR(5),
~mdw / disorder / blob