- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,8 +1,15 @@
-Information where applier is set (classes or objects) should be only stored on
the originating node where the applier is set.
+Information where applier is set (on classes or objects) should be only stored
on the originating node where the applier is set.
-Today, object and class applier set is done over fevs, and this information is
stored on all nodes. Newly synced node does not have information where the
applier is set.
-Detaching the applier from the originating node and attaching to the new node
may have have different behavior then attaching the applier again to the
originating node or some veteran node.
+Today, object and class applier set, using saImmOiObjectImplementerSet() and
saImmOiClassImplementerSet(), is done over fevs, and this information is stored
on all nodes. Newly synced node does not have information where the applier is
set.
+Detaching the applier from the originating node and attaching to the new node
may have different attached objects and classes then attaching the applier
again to the originating node or some veteran node.
This means that if the applier is set to a new object or class, it may get
different callbacks on veteran nodes (including the originating node) and new
nodes.
-Appliers are only of interest on the local node. Where applier is set (object
or class) is not of interest for remote nodes.
-Object/class applier set should be stored locally.
+Appliers are weak, and applications must set applier again to objects and
classes after applier is set by saImmOiImplementerSet().
+
+Applier bindings are only of interest on the local node. Object and class
applier bindings are not of interest for remote nodes.
+
+This patch should make object and class applier set info consistent per node.
+This means that applier set (saImmOiImplementerSet() ) will bind objects and
classes that have alredy been bound on the local node by the same applier name.
+
+Applier set (using saImmOiImplementerSet() ) will work as it works today.
Applier name and applier id will be stored on all nodes.
+Object and class applier set (using saImmOiObjectImplementerSet() and
saImmOiClassImplementerSet() ) will only be done on local immnd, and will not
be sent to all nodes like it works today.
~~~~
- **status**: unassigned --> accepted
- **assigned_to**: Zoran Milinkovic
---
** [tickets:#1535] imm: class and object applier set should be only on local
immnd**
**Status:** accepted
**Milestone:** 5.0
**Created:** Fri Oct 09, 2015 01:44 PM UTC by Zoran Milinkovic
**Last Updated:** Fri Oct 09, 2015 01:44 PM UTC
**Owner:** Zoran Milinkovic
Information where applier is set (on classes or objects) should be only stored
on the originating node where the applier is set.
Today, object and class applier set, using saImmOiObjectImplementerSet() and
saImmOiClassImplementerSet(), is done over fevs, and this information is stored
on all nodes. Newly synced node does not have information where the applier is
set.
Detaching the applier from the originating node and attaching to the new node
may have different attached objects and classes then attaching the applier
again to the originating node or some veteran node.
This means that if the applier is set to a new object or class, it may get
different callbacks on veteran nodes (including the originating node) and new
nodes.
Appliers are weak, and applications must set applier again to objects and
classes after applier is set by saImmOiImplementerSet().
Applier bindings are only of interest on the local node. Object and class
applier bindings are not of interest for remote nodes.
This patch should make object and class applier set info consistent per node.
This means that applier set (saImmOiImplementerSet() ) will bind objects and
classes that have alredy been bound on the local node by the same applier name.
Applier set (using saImmOiImplementerSet() ) will work as it works today.
Applier name and applier id will be stored on all nodes.
Object and class applier set (using saImmOiObjectImplementerSet() and
saImmOiClassImplementerSet() ) will only be done on local immnd, and will not
be sent to all nodes like it works today.
---
Sent from sourceforge.net because [email protected] 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets