[asterisk-app-dev] Standardization of Case for ARI URIs

[Leif Madsen]

I agree with Paul here. Lets assume we're working with a standard web
type interface and not have a preferred uppercase convention just
because "that's how Asterisk has always done it".

The preference should be for lowercase throughout, except for any
channel or peer identifiers which need to be case sensitive due to
naming conventions.

Leif.

-----Original Message-----
From: Paul Belanger <paul.belanger at polybeacon.com>
Reply-to: Asterisk Application Development discussion
<asterisk-app-dev at lists.digium.com>
To: Asterisk Application Development discussion
<asterisk-app-dev at lists.digium.com>
Subject: Re: [asterisk-app-dev] Standardization of Case for ARI URIs
Date: Mon, 20 Jan 2014 15:45:36 -0500

Personally, I prefer everything to be lower case when possible.  So,
things like TECH, if PJSIP, pjsip, PjSiP, are all valid inside
asterisk, lets round down to pjsip.  However, if ENDPOINT is case
sensitive in Asterisk, then expect the end user to enter it as such.

So using your example above:

127.0.0.1:8088/ari/endpoints/pjsip/200

or

127.0.0.1:8088/ari/endpoints/pjsip/FooBar

or

127.0.0.1:8088/ari/endpoints/pjsip/foobar

All return different endpoints.

Additionally, have we even considered embedding the actually resource
URL when we list an object in the return result? Then Asterisk can
tell the user exactly how to get a specific item in the list.

For example, we create a links: [] object, that would list the actual
URI for said item.




-- 
Leif Madsen
Lead UC Systems Engineer
c: +1-613-800-7610
http://thinkingphones.com