Re: Separation of protocol and information model

[Bobby Krupczak <rdk@krupczak.org>]

Hi!

>Bobby Krupczak writes:
>>Interesting; however, the vipw program has to use linked code that has
>>intimate details of the file structure and code that converts that
>>code into an in-memory structure.
>
>I don't follow you here; are you talking about pw_mkdb()? This is
>the equivalent of <commit-configuration/> in the netconf case, since
>pw_mkdb checks the data and parcels it out to the rest of the system.
>In the netconf case, the code invokes a series of RPC to the device.

All of these programs use c-libraries which load, lock, parse,
read/write/convert etc.  So, its difficult to separate them out so
cleanly.  While each layer is a little bit removed, changes in one
area (e.g. the libraries) have rippling effects on the rest of the
code.

Bobby

--
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/>