Re: Issue 5.1 Wrap-up: SSH End of message directive

[Ed Roskos <Ed.Roskos@utstar.com>]

I suppose it has to be invalid XML to meet the 3rd criteria, so we may
even get rid of making it look like a processing instruction and go with
something a bit easier to see as an end-of-message marker.

But I personally still believe it is better to use valid XML and to
forbid a NetConf agent from generating a CDATA block with the eom
embedded in it.  If we go with a non-XML eom, then it discounts the
ability to send off a bunch of request documents and a drop-connection
and to wrap the whole sequence in an XML element so you can use the
sequence of replies in a single document parsed by the original
requester.  This allows a single DOM for the replies (if desired for
a given application) or to use XSLT on the full set of replies.

> Hi,
>
> There seems to be consensus that:
>  - we should have a NETCONF-specific framing mechanism for SSH
>  - we should select an "end of message" character sequence that 
>    should not be present in an XML instance document, such as <?eom?>
>  - we should select a sequence that is not legal in a CDATA section
>    and not rely on a low probability of the sequence occurring 
>    accidentally
>
> So, what is this character sequence?
>
>
> Andy
>
>
> --
> 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/>
>  



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