Re: Netconf over SOAP

[Ted Goddard <ted.goddard@windriver.com>]

On Tuesday, October 28, 2003, at 01:47 AM, Mi-Jung Choi wrote:

> => The advantage of SOAP over BEEP and SSH is to use RPC mechanism.
> But the use of <rpc> tag prevented the manager from directly calling
> base operations
> such as <get-config>, <edit-config> and etc.  So the advantage of SOAP
> RPC
> disappears and the use of SOAP may cause overhead.

The call is not "direct" with <rpc>, but the differences between
with <rpc> and without <rpc> are largely cosmetic:

agent.rpc(GetConfig g);   (with <rpc>)
  vs
agent.getConfig();        (without <rpc>)

> SOAP implementation automatically encodes SOAP RPC message by calling
> RPC operations.
> Developers using SOAP environment do not need to implement the message
> encoding portion
> unlike BEEP and SSH. But they must know the parameters and return 
> values
> of RPC operations.

I agree, there are many benefits from using SOAP-related code generation
tools.

> So, we mentioned the use of WSDL as the description of RPC operations
> for using RPC mechanism.
> To improve interoperability, the parameters of RPC operations must be
> defined
> in NETCONF over SOAP.

Indeed, the WSDL given in draft-ietf-netconf-soap-00.txt
imports the NETCONF base schema with its defined types and this
can used to generate source code corresponding to those types.

Ted.


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>