Re: Update to Netconf Notifications Draft

[Martin Bjorklund <mbj@tail-f.com>]

Hi,

A comment on section 3.8, interleaving messages.

Suppose the manager sends a large copy-config and at the same time the
agent sends a large notification.  If care is not taken, the write()
call on each side can block, and we would get deadlock.  To avoid
this, the manager and/or agent could be required to use non-blocking
io, and - while writing the large message - read from the session and
buffer internally.  Alternatively, the agent could use two threads.

Should any of this be specified?  Does a client application which
supports interleaving messages have to use non-blocking io in order to
be compliant (or should the agent handle this)?


/martin

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