Yes - I agree... empty string is better. Indeed I would go so far as to say the spec should be changed to remove the need for a leading forward-slash in a virtual host name (it is just a wasted-byte!). Banning forward slashes altogether from the name would be even better :-)
To be completely clear, for the "default" virtual host, are we talking about i) A virtual host with name "", completely separate from all other virtual hosts or ii) A mapping from one of the specified named virtual hosts to the default "" name (i.e. the same virtaul host is addressed by multiple names). Option i) is anaologous to the default exchange I think. Option ii) is more like what you expect in Apache HTTPD type config (where you can map many names to the same virtual host). I prefer ii) but i) is more "AMQP" ... - Rob On 06/02/07, Gordon Sim <[EMAIL PROTECTED]> wrote:
Alan Conway wrote: > I'll JIRA for the C++ client to default to the empty string, unless > someone knows why "/" is a reasonable default for a virtual host name. Once upon a time the AMQP spec stated that all virtual hosts had to start with a '/' and that all brokers should support '/' (the default) and '/sandbox' (for conformance testing!). That is by way of background explanation only and is no longer the case. I agree that the empty string is better.
