Issue 1706:  comment_*() operations needed in CosNotifyComm Interface (notif_service-rtf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: One of the missing pieces in the Notification Service is that
 connect_*() operations are needed on the CosNotifyComm interfaces.  That
 way a third party can connect the end points and channel together.  With
 the current spec the end points have to connect them self to the channel
 or a third party needs to know the proprietary extensions of the
 endpoint to set up the connection.  The endpoints that ALWAYS connect
 themself to the channel could throw the NO_IMPLEMENT exception.
 
 
 

Resolution: 
Revised Text: 
Actions taken:
July 20, 1998: received issue
February 23, 1999: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <tim@protocol.com>
Sender: tim@protocol.com
Date: Mon, 20 Jul 1998 10:25:14 -0700
From: Tim Brinson <tim@protocol.com>
Organization: Protocol Systems, Inc.
To: "Michael J. Greenberg" <mjg@syl.nj.nec.com>, issues@omg.org,
        juergen@omg.org
Subject: Re: One correction...
References: <199807092039.QAA15446@syl.syl.nj.nec.com>
<35AAAC10.18D452E8@protocol.com>

Juergen,

I never saw an issue number generated for this.

Thanx,

Tim


Tim Brinson wrote:
> 
> Michael J. Greenberg wrote:
> > My proposal would be to define new PushConsumer, PushSupplier,
> PullConsumer,
> > and PullSupplier interfaces within CosNotifyComm that multiple
> > inherit from their CosEventComm equivalent, and either
> NotifyPublish (for the
> > Consumer interfaces) or NotifySubscribe (for the Supplier
> interfaces). Then,
> > these new interfaces could be passed as input to the appropriate
> > connect_* operations supported by their corresponding proxy.
> >
> > I'm interested in comments.
> 
> Mike,
> 
> While this is not the exact problem we had with using Notifications
> with
> PIDS it is in a related area.
> 
> One of the missing pieces in the Notification Service is that
> connect_*() operations are needed on the CosNotifyComm interfaces.
> That
> way a third party can connect the end points and channel together.
> With
> the current spec the end points have to connect them self to the
> channel
> or a third party needs to know the proprietary extensions of the
> endpoint to set up the connection.  The endpoints that ALWAYS
> connect
> themself to the channel could throw the NO_IMPLEMENT exception.
> 
> Tim
> 
>
>
> ------------------------------------------------------------------------
> 
>                       Name: vcard.vcf
>    vcard.vcf          Type: VCard (text/x-vcard)
>                   Encoding: 7bit
>                Description: Card for Tim Brinson