Il 07/09/2012 12:03, Daniel P. Berrange ha scritto: >> > I think doing it the other way round would be more logical: >> > >> > gluster+unix:///path/to/unix/sock?image=volname/image >> > >> > This way you have the socket first, which you also must open first. >> > Having it as a parameter without which you can't make sense of the path >> > feels a bit less than ideal. > The issue here is that the volume/path/to/image part is something that is > required for all gluster transports. The /path/to/unix/sock is something > that is only required for the unix transport. To have consistent URI > scheme across all transports, you really want the volume/path/to/image > bit to use the URI path component.
I was writing the same---plus, perhaps there is a default for the Unix socket path, so that in the common case you could avoid the parameters altogether? Paolo
