Scott wrote:
...
> > So given that there will be one REST request per config file, does
> > this make sense?
> >
> > /phone/{phoneId}/profile/{name} - GET
> >
> > Where the body of the HTTP response would be the configuration file
> > verbatim.
>
> What is {name}, and can it contain slashes?
It's the configuration file name. Would {filename} be better?
Excellent point about the slashes, as some config files are stored in
subdirectories. (e.g. Nortel IP 12x0's Nortel/config/SIP<<<MAC>>>.xml.)
URL encoding the filename would solve that problem.
> > - /phone?serialNumber={serialNumber} GET to query for a phone by
> > serial number. Example response XML body:
> > <phone>
> > <phoneId>4</phoneId>
> > <serialNumber>0004f21ed0d3</serialNumber>
> > <model>polycom650</model>
> > <description>Some text...</description>
> > </phone>
>
> Why return all that other data? Why not just a redirect to
> the serial number version of the url?
I hadn't proposed a serial number version of the URL, because serial
numbers change. (A PUT to a URL that invalidates the URL seems odd.)
I'm happy to live with that though, since sipXprovision doesn't need to
change serial numbers. It would indeed be easier for everyone.
(In this case the existing POST on /phone could or should have been
implemented as a PUT on /phone/{serialNumber}.)
Damian wrote:
...
> GET /phone/{serialNumber}/profile
>
> Needs to retrieve the list of profiles (for completeness).
sipXprovision doesn't have a need for it, but no objection from me.
-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/
