[Openais] RE: [saf-open] Open channels, retained events, cluster partition merges.

Saha Sayandeb-G19428 sayandeb.saha at motorola.com
Wed Feb 16 12:27:45 PST 2005


Mark & Steven,

This is rather an elaborate mail thread but I'll try to briefly address
some of the questions you raise...

1. Most SAF services API were designed with a Unix/Posix look and feel
and that's one of the reasons you see the event channel unlink API described the
way it is. Also a conscious effort was made to align the common API 
create/open/close/unlink API amongst the various services like EVT, MSG,
CKPT etc. So sometimes you'll find certain features which apparently look 
useless but might be there for consistency reasons.

2. The above simplifies implementation in a normal cluster as the clients
which have the channels open needn't be back-informed that the channel which they had opened 
is gone and they need to re-open it if they want to use it.

3. I am pretty sure that post cluster merge/partition semantics for the various logical
objects like event channel, message queue etc were not given as much thought. But
I would agree with Steve's scenario description.


Sayan

> -----Original Message-----
> From: saf-open-bounces at lists.osdl.org 
> [mailto:saf-open-bounces at lists.osdl.org] On Behalf Of Mark Haverkamp
> Sent: Thursday, February 10, 2005 2:23 PM
> To: Steven Dake
> Cc: Openais List; SAF Open List
> Subject: Re: [saf-open] Open channels, retained events, 
> cluster partition merges.
> 
> 
> On Thu, 2005-02-10 at 12:15 -0700, Steven Dake wrote:
> > Mark
> > 
> > I wasn't contributing during the specification of this 
> wording of the
> > unlink so I am unsure.  This question might be appropriate for the
> > saf-open list though.  Perhaps some of the saf spec 
> developers may have
> > some ideas.
> > 
> 
> Yes, that is the very reason that i copied that list on my mail.
> 
> Mark.
> -- 
> Mark Haverkamp <markh at osdl.org>
> 
> 



More information about the Openais mailing list