Il 06/09/2012 17:40, Bharata B Rao ha scritto: > > > > I don't think we can fit 'unix' within the standard URI scheme (RFC > > > > 3986) > > > > easily, but I am planning to specify the 'unix' transport as below: > > > > > > > > gluster://[/path/to/unix/domain/socket]/volname/image?transport=unix > > > > > > > > i,e., I am asking the user to put the unix domain socket path within > > > > square brackets when transport type is unix. > > > > > > Never saw something like this before, but it does seem reasonable to me. > > > Excludes ] from the valid characters in the file name of the socket, but > > > that shouldn't be a problem in practice. > > > > Bikeshedding, but I prefer > > > > gluster:///path/to/unix/domain/socket:/volname/image?transport=unix > > Unless you or others strongly feel about this, I would like to go with > [ ] based spec, which I feel is less prone to errors like missing a colon > by mistake :)
Your proposed spec has the disadvantage of not being a proper URL. What about this instead: gluster:///path/to/unix/domain/socket!/volname/image?transport=unix since (http://www.w3.org/Addressing/URL/uri-spec.html) "The asterisk ("*", ASCII 2A hex) and exclamation mark ("!" , ASCII 21 hex) are reserved for use as having special signifiance within specific schemes". Paolo
