- **Milestone**: 4.7.2 --> 5.2.FC
---
** [tickets:#2020] AMF : Additional features for csiAttributeChangeCallback **
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Sat Sep 10, 2016 05:53 AM UTC by Srikanth R
**Last Updated:** Sat Sep 10, 2016 05:53 AM UTC
**Owner:** nobody
The following features can be considered additionally for
csiAttributeChangeCallback implementation.
-> Currently both active and standby receives csiAttributeChangeCallback
simultaneously. But csiAttributeChangeCallback should be handled in a way like
csiSet callback. Initially Component with active assignment should receive the
callback and later the standby should receive.
There might be scenario in user application that standby shall try to access
an object, which is associated with a CSI and should be created by active. If
both the components simultaneously gets callback, then standby may behave
erroneoulsy if it processes the callback before a busy active component
processes the callback.
-> Currnelty, the csiAttributeChangeCallback is invoked only when values are
added to existing csi attrib class. But if a new csi attribute class is
created, callback is not invoked.
Callback should be invoked for every modification of csi attrib objects. All
the operations create, modify and delete should be supported.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets