[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 5.1 Wrap-up: SSH End of message directive
>>>>> Ed Roskos writes:
Ed> I suppose it has to be invalid XML to meet the 3rd criteria, so we
Ed> may even get rid of making it look like a processing instruction
Ed> and go with something a bit easier to see as an end-of-message
Ed> marker.
Ed> But I personally still believe it is better to use valid XML and
Ed> to forbid a NetConf agent from generating a CDATA block with the
Ed> eom embedded in it. If we go with a non-XML eom, then it
Ed> discounts the ability to send off a bunch of request documents and
Ed> a drop-connection and to wrap the whole sequence in an XML element
Ed> so you can use the sequence of replies in a single document parsed
Ed> by the original requester. This allows a single DOM for the
Ed> replies (if desired for a given application) or to use XSLT on the
Ed> full set of replies.
I fail to understand your argument here. The <?eom?> marker is there
only for the SSH mapping because it does not do proper framing. The
<?eom?> marker should be inserted when the document hits the SSH
transport and removed once if comes out of the SSH transport and this
should be totally transparent for any "higher level" processing of the
NETCONF XML messages. Note that the NETCONF messages themself continue
to be XML documents. So if you want to transform NETCONF XML documents
using XSLT or embed them in another XML document, just do so.
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
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/>