Re: Notification Message Processing Model

[Steve Berl <sberl@cisco.com>]

The most widely implemented and deployed example of the "never ending reply
XML" is Jabber. There are dozens, if not hundreds of implementations of this
in many different implementation languages. So the argument that it would be
too hard for a manager to implement seems a bit questionable.

-steve

On 3/24/06 7:33 AM, "Phil Shafer" <phil@juniper.net> wrote:

> Balazs Lengyel writes:
>> I feel that using a never ending rpc-reply is a much bigger deviation from
>> the original 
> 
> But it's not a deviation; it's completely within the spec.  For
> example, JUNOScript has a <ping> RPC.  When you perform this RPC,
> the ping operation continue until the connection is terminated or
> the <abort/> operation is sent.  There's another RPC called
> <get-accounting-record-information> which will feed you accounting
> records with the same unending paradigm.  The endless reply is
> really quite useful.  Yes, it requires your client to understand
> that it cannot buffer data endlessly before passing it up to
> interested parties, but a <get-route-information> RPC on a box
> with a million routes will do this too.
> 
> 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/>

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