[Openais] API inconsistency - evs callback functions

Steven Dake sdake at redhat.com
Wed Jul 1 11:58:56 PDT 2009


On Wed, 2009-07-01 at 14:52 +0200, Wojtek Meler wrote:
> Wojtek Meler pisze:
> > I've noticed a little API inconsistency. Every corosync service defines 
> > callbacks which receive handle obtained from initialize function as 
> > first argument.
> > EVS is different - callbacks don't get handles. Without them one is 
> > forced to use global / thread variables to remember which handle is 
> > passed to evs_dispatch.
> > Is there any chance to fix API in near future?
> >
> >   
> Deliver callback doesn't have group name too :(. There is no way to 
> discover it....
> I'm quite confused. How cpg differ from evs?  How should I decide which 
> service I should use?
> 

EVS is used for virtual synchrony passthrough.  It has the concept of
groups only so multiple applications can use EVS.  Generally unless you
are creating an application that requires EVS details, you will want to
use CPG.

CPG provides a lightweight closed process group membership layer ontop
of the membership layer provided by totem.  I recommend CPG for all
development related to clustering since it provides a better membership
model.

Regards
-steve

> Regards,
> Wojtek
> _______________________________________________
> Openais mailing list
> Openais at lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/openais



More information about the Openais mailing list