[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 5.1) SSH End of message directive


However, if the connection is closed in such failure cases, it makes
putting each operation in its own XML document less compelling.

The single-document-session form is easier to implement, and would
allow NETCONF implementations to borrow "streaming" XML parsing code
from existing Jabber projects.  The one restriction would be you
can't use a DOM parser to implement NETCONF/SSH.

One substantial benefit to the single document form is that a group
of namespaces could be declared for all operations in the session.

Ted.

On Dec 16, 2003, at 3:26 PM, Rob Enns wrote:

On Tue, Dec 16, 2003 at 04:38:52PM -0500, Phil Shafer wrote:
Ted Goddard writes:
Should the connection be closed upon any XML well-formedness errors? 

Yes, since with out a framing protocol, there is no way to reliably
recover the connection.  The two peers cannot agree on what the
state of the connection is, which means that one side could hang
waiting on the other side to send data that will never come.  The
possibility of hanging and the probability of dropping data go
strongly against the sort of exactness one wants in an API.


... and I don't think this is too severe for cut'n'paste users,
because folks to cut'n'paste to see how the protocol works, and
to debug script problems. People that want a forgiving environment
for other reasons will use the CLI.

thanks,
 Rob



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