[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 5.1) SSH End of message directive
- To: Phil Shafer <phil@juniper.net>
- Subject: Re: Issue 5.1) SSH End of message directive
- From: Rob Enns <rpe@juniper.net>
- Date: Tue, 16 Dec 2003 14:26:09 -0800
- Cc: Ted Goddard <ted.goddard@windriver.com>, netconf@ops.ietf.org, Mark Stahl <mark.stahl@utstar.com>, "David T. Perkins" <dperkins@dsperkins.com>, Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>, Graham Klyne <GK-lists@ninebynine.org>
- In-reply-to: <200312162138.hBGLcqBE057724@idle.juniper.net>
- Mail-followup-to: Phil Shafer <phil@juniper.net>, Ted Goddard <ted.goddard@windriver.com>, netconf@ops.ietf.org, Mark Stahl <mark.stahl@utstar.com>, "David T. Perkins" <dperkins@dsperkins.com>, Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>, Graham Klyne <GK-lists@ninebynine.org>
- References: <A1D1F7A4-300C-11D8-9C0E-003065C0229A@windriver.com> <200312162138.hBGLcqBE057724@idle.juniper.net>
- User-agent: Mutt/1.4i
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/>