Azure Service Bus supports "/" character for sure in the queue or topic names. Just a curiosity about that ...
With the old Azure portal you can create a queue named "test/slash" but you cannot do that in the new Azure portal because it uses the ARM deployment (Azure Resource Manager) where "/" is used as separator for resources. In this case you have to create the
queue using the "~" so "test~slash" but then the Service Bus will create the queue with "test/slash" name.
If you are curious, more here : https://blogs.msdn.microsoft.com/servicebus/2017/06/21/azure-service-bus-azure-resource-manager-and-this-character/
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor
From: hono-dev-bounces@xxxxxxxxxxx <hono-dev-bounces@xxxxxxxxxxx> on behalf of Hudalla Kai (INST/ECS4) <kai.hudalla@xxxxxxxxxxxx>
Sent: Wednesday, July 26, 2017 12:48 PM
To: hono developer discussions
Subject: Re: [hono-dev] Custom path separator character
Maybe it would be worthwhile to check, if other AMQP 1.0 compliant brokers support slashes in addresses before we ultimately remove it.
Does anybody know if other services/brokers (e.g. Azure Service Bus) have such limitations?
Mit freundlichen Grüßen / Best regards
Kai Hudalla
Chief Software Architect
Bosch Software Innovations GmbH
Schöneberger Ufer 89-91
10785 Berlin
GERMANY
www.bosch-si.com
Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B;
Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
From: hono-dev-bounces@xxxxxxxxxxx <hono-dev-bounces@xxxxxxxxxxx> on behalf of Dejan Bosanac <dejanb@xxxxxxxxxxxx>
Sent: Wednesday, July 26, 2017 14:07
To: hono developer discussions
Subject: Re: [hono-dev] Custom path separator character
+1 from me as well (as a guilty one for this). We don’t need it anymore