aboutsummaryrefslogtreecommitdiffstats
path: root/doc/protocol.xml
diff options
context:
space:
mode:
authorMax Kellermann <max@duempel.org>2015-02-09 07:55:06 +0100
committerMax Kellermann <max@duempel.org>2015-02-09 07:55:06 +0100
commit676dfabc91b5f9b0ff54ce145a34352fe0a43202 (patch)
treef9f5f28f632492583aa211ab9cc4ff9aee9a0e8f /doc/protocol.xml
parent60e6d1d61b1c56d3a94fa73779f240b8d7d43a89 (diff)
downloadmpd-676dfabc91b5f9b0ff54ce145a34352fe0a43202.tar.gz
mpd-676dfabc91b5f9b0ff54ce145a34352fe0a43202.tar.xz
mpd-676dfabc91b5f9b0ff54ce145a34352fe0a43202.zip
command/{Queue,File}Commands: drop "file:///" prefix for absolute paths
Requiring this prefix makes the client's intention very clear, but it was too hard to understand why this prefix was needed. Initially, my intention was to differentiate from broken clients which prefix relate URIs with a slash; once MPD allowed that. In the past few years however, MPD has disallowed that, and there was no significant breakage (except for the "add /" special case which some clients apparently still do). So I figure it's about time to define that an URI that begins with a slash points to an arbitrary file on the file system.
Diffstat (limited to '')
-rw-r--r--doc/protocol.xml5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/protocol.xml b/doc/protocol.xml
index 49bc20160..f9f8ea346 100644
--- a/doc/protocol.xml
+++ b/doc/protocol.xml
@@ -1772,7 +1772,7 @@ OK
<para>
Clients that are connected via UNIX domain socket may
use this command to read the tags of an arbitrary local
- file (URI beginning with "file:///").
+ file (URI is an absolute path).
</para>
</listitem>
</varlistentry>
@@ -1787,8 +1787,7 @@ OK
<para>
Read "comments" (i.e. key-value pairs) from the file
specified by "URI". This "URI" can be a path relative
- to the music directory or a URL in the form
- "file:///foo/bar.ogg".
+ to the music directory or an absolute path.
</para>
<para>
This command may be used to list metadata of remote