[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: event classes (sec. 3.5)

Phil Shafer wrote:

Andy Bierman writes:

How do you distinguish delayed responses for this ping
vs. other delayed responses. vs other RPCs?


It's a long-lived RPC.  The rpc-reply contains the entire results.


Are you willing to help write an Informational RFC so those who
like it can all do long-lived RPC in the same way?

It seems to me this can make the parsing easier on the NMS, not harder.
Consider an iterator operation that get-nexts its way through really
big tables.  This is not an endless RPC, just a really long RPC
where perhaps an <ok> (to ACK the initial request) is followed by N <data>
nodes.   If the RPC is intended to end (or <abort/> is received),
the </rpc-reply> element will be sent and the PDU ended.

The difference is that instead of a really big XML tree, the NMS
can consume multiple "rows" in sequence, where each <data>
element is well-formed XML and represents a conceptually
coherent container of data. (or like, notification data even ;-)





If not that, then how do you distinguish multiple responses to
1 request?


We don't have 'em.  It's a one-to-one mapping.

Thanks,
 Phil




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