Re: Issue 5.1) SSH End of message directive

[Phil Shafer <phil@juniper.net>]

Ted Goddard writes:
>that leads us back to having each operation as a standalone
>document.

Cool.

>The following malformed session raises the importance of the
>end-of-message marker:
>
>     <rpc>
>       <set-config/>
>     <!-- missing rpc tag will corrupt the next operation -->
>     <rpc>
>       <validate/>
>     </rpc>

This is an example of a broken protocol or framing protocol error
that would force the server to close the connection.

>Note, however, that this argues against the use of a simple 
>pre-processor,

And argues for a real framing protocol

>not against the use of <?eom?>.  <?eom?> could still be correctly 
>detected by
>an XML parser.

How would it be detected in your CDATA case?

Thanks,
 Phil

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