remote APIs
- From: Guy Hulbert <gwhulbert (at) eol.ca>
- Date: Fri, 03 Feb 2006 10:30:38 -0500
Thanks Douglas. Very enlightening.
On Fri, 2006-03-02 at 10:06 -0500, Douglas Hubler wrote:
> Guy Hulbert wrote:
<snip>
> If sipXconfig is on another machine, it would off load some work
> resources. About 50% of app can be remoted now, there's still more to
> do to get full functionality when separated on a different machine.
>
>
> http://sipx-wiki.calivia.com/index.php/Installing_sipXconfig_on_a_Separate_Machine
thanks
> http://track.sipfoundry.org/browse/XCF-904
>
> >Or do you have a Java piece which talks to a C++ piece via SOAP so you
> >don't have to run Java on the boxes where you are saving CPU cycles ?
> >
> >
> Soap is API _from_ sipXconfig. Only APIs _from_ other sipX components
> is the CGIs and XMLRPCs noted above.
I thought SOAP evolved as a replacement for XMLRPC ...
--
--gh
_______________________________________________
sipx-dev mailing list
sipx-dev (at) list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-dev
- Follow-Ups:
- remote APIs
- From: Douglas Hubler <dhubler (at) pingtel.com>
- remote APIs
- From: Walter Gillett <wgillett (at) pingtel.com>