RE: Detailed locking

["Rob Enns" <rpe@juniper.net>]

Fine grained locking was deferred from the 1.0 protocol spec,
in the interest of simplicity. You're quite right about the limitations
of the global lock, I'm sure fine grained locking will be high
on the list of post 1.0 work items.

Rob 

> -----Original Message-----
> From: owner-netconf@ops.ietf.org 
> [mailto:owner-netconf@ops.ietf.org] On Behalf Of Balazs Lengyel
> Sent: Wednesday, November 16, 2005 1:59 AM
> To: netconf@ops.ietf.org
> Subject: Detailed locking
> 
> What is the reason that we only allow locking of a complete datastore.
> 
> Ericsson might need a more fine grained locking mechanism. 
> E.g. If we have subscriber data 
> and device configuration data in the same node one manager 
> might be updating the 
> subscriber data while the other migh be changing OSPF 
> settings. It could work perfectly as 
> the two areas are quite separate. However if you lock the 
> whole configuration this is not 
> possible.
> 
> -- 
> Balazs Lengyel                       Ericsson Hungary Ltd.
> 
> --
> 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/>