Hi Martin,
> The java code is still using amqp-0.8 which as Gordon says requires a > leading '/'. The java client url parsing requires the '/' for the url > to be well formed. The java broker never enforced an initial '/' so > when the vhost implementation was done it was done with out the '/'. > Which made sense as it is a wasted byte in network traffic. So > currently I believe the client code strips off the '/' after verifying > the vhost before sending over the wire to save that extra byte. Actually, it doesn't strip it; it adds it if it's missing. At least on the code in the trunk (haven't switched to M2). The .NET client then would have a bug; because unlike the Java code, it doesn't add a leading '/' to the virtual host path when creating a connection without a connection URL. Tomas Restrepo http://www.winterdom.com/weblog/
