Re: Issue 5.1) SSH End of message directive

[Phil Shafer <phil@juniper.net>]

Ted Goddard writes:
>Are there failure modes that people are thinking of that this
>fundamentally doesn't handle?

The big problem is languages like java, where the parser takes
control of your thread and does not return until either an error
occurs or it reads an EOF indication.  It's trivial to wrap an
InputSource with a class that returns a false EOF when it sees a
simple marker like "<?eom?>".  Making it truly parse XML is not
so trivial since you've got to deal with namespaces and prefixes.

http://java.sun.com/xml/jaxp/dist/1.1/docs/api/org/xml/sax/Parser.html

Another concern is recovering from error, when 'return' or 'exit'
won't suffice.  If you need to detect the end of the current data
set/rpc after the xml parser has thrown an error, you need some
sort of simple framing.

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