Is Period the best parts separator for Queue/Topic/Subscription Paths?

[michaelnoonan]

The default parts separator for creating the Path to service bus entities in Nimbus is '.' (a period) which is fine in most situations though it can be problemmatic in URLs.

A specific example is that by default IIS will treat a request ending with something that looks like a file as a request for a static resource and returns 404 when it can't find the file on the file system. You can work around this by adding a trailing '/' to the URL or by specifically adding an exception in web.config.

I'm just wondering if period is the most appropriate parts separator?

Perhaps Nimbus could offer some customisable conventions?

[DamianMac]

I'm a bit confused by this, I get what you're saying about IIS.. but are you trying to address a queue in a way that you're getting a 404 ?
We don't have a lot of options that are valid on azure, we can use an underscore, a period or a hyphen.

[michaelnoonan]

Yeah, it's not really related to running Nimbus as a Service Bus, but I
bumpted into a problem getting dead letter management working.

I was using the queue path as part of the URL in a web request to get dead
letters from the $DeadLetter subqueue (for which you need the original
queue path), and subsequently destroying or replaying them.

For example: DELETE /deadletters/q.myqueue

IIS responded to this request with a 404 treating "q.myqueue" as a file
that wasn't found.

Appending a '/' to the end of the URL fixed the immediate problem:
For example: DELETE /deadletters/q.myqueue/

Just thought to ask the question in case there was a more universally
acceptable parts separator Nimbus could use out of the gate, like hyphen,
that wouldn't cause the unsuspecting developer confusion when tackling
problems like this.

Either way this is probably a corner case and could happily be ignored.

On Thu, Feb 13, 2014 at 4:25 PM, Damian Maclennan
notifications@github.comwrote:

I'm a bit confused by this, I get what you're saying about IIS.. but are
you trying to address a queue in a way that you're getting a 404 ?
We don't have a lot of options that are valid on azure, we can use an
underscore, a period or a hyphen.

Reply to this email directly or view it on GitHubhttps://github.com/DamianMac/Nimbus/issues/43#issuecomment-34951859
.

[uglybugger]

This is a known pain in the backside when dealing with MVC routing on IIS - it treats anything with a . that doesn't precede a slash as a static filename rather than a parameter.

Not sure how much we want to care about it in this context, though - is it likely to come up often? Thoughts?