Damian wrote:
> >> Excellent point about the slashes, as some config files
> are stored in
> >> subdirectories. (e.g. Nortel IP 12x0's
> >> Nortel/config/SIP<<<MAC>>>.xml.)
> >
> > ... and more should be, since we're going to have to bite
> the bullet
> > soon and support multiple versions of firmware for phones, which is
> > going to be easily implemented using subdirectories for some of the
> > files.
>
> This seems unrelated.
Agreed. I know which files Scott is referring to, and none are
generated by sipXconfig.
> > I'm not sure what problem you mean - since it's the end of the url,
> > just leave the slashes alone.
> >
> >
>
> Many REST server libs split URLs by slashes: supporting
> unquoted slashes as a {name} might turn out to be be
> unnecessarily awkward.
> Please remember that profile "name" is not the same as "file
> name". Maybe we don't need slashes in profile names at all.
sipXprovision has a base URL, and phones will make a GET request
relative to that, e.g. "Nortel/config/SIP<<<MAC>>>.xml" or
"polycom-<<<MAC>>>.cfg". My work is easier if sipXprovision doesn't
need to selectively drop path components from these values when
constructing the REST request URI.
This should be the easier option for sipXconfig too, because these
strings match what's returned from Device.getProfileTypes() (as used by
the profile preview links.)
Scott wrote:
> > - /phone/{phoneId} GET should return the same XML body as above.
> > (sipXprovision won't need this GET, but it seems useful to have for
> > consistency.)
>
> I don't think we should build anything that we don't
> currently have any use for.
I agree 100% with that statement.
But in this case, we're talking about an API available to third parties.
Preferably it will be complete enough to be useful beyond the very
narrow requirements of sipXprovision.
-Paul
[email protected]
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
