Xingjun Chu wrote: > Hi , > > > > I am using REST API click to call for some integration work and got an > issue with it. Since some web proxy doesn't support "PUT", some of my > work doesn't work. > > > > So just wondering why uses "PUT" for the REST API other than for example > "GET", what's the design intent? >
PUT makes more semantic sense (you are "setting" the call instance). > > > Also when using "PUT", some web server expects content length > 0, so > everytime I have to put some "dummy" in the content to make web server > happy. > Yes. That's a restlet issue... > > > I would like to suggest to use "GET", but no sure what's the consequence. > sipXconfig (via restlet) also supports POST tunneling for those clients and proxies that cannot issue anything but GET and POST... http://www.restlet.org/documentation/1.0/api/org/restlet/service/TunnelService.html It would look something like: POST https://{user}:{passwo...@{host}:8443/sipxconfig/rest/call/{number}?methodParameter=PUT That said - since GET is not used for anything useful, I can change it so that GET and PUT do the same thing. [...] BTW: ranga is actually working on a call server service that will at some point take over from sipXconfig in providing set=up call services. D. _______________________________________________ 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/
