Issue 3300: DIIPollable also needs to be an abstract valuetype like Pollable. (messaging-rtf)
Source: Ericsson (Mr. Chris Smith, nobody)
Nature: Uncategorized Issue
Severity: 
Summary: Messaging RTF 1.2 adopted a resolution that changes
Pollable from an interface to an abstract valuetype.
DIIPollable inherits from this, and so also needs
to be changed to be a valutype (probably an  abstract 
one).

Resolution: resolved
Revised Text: 
Actions taken:
February 7, 2000: received issue
January 9, 2001: closed issue
Discussion: 
Change definition of DIIPollable in Corba Core from 
interface DIIPollable : Pollable {}; 

to 

abstract valuetype DIIPollable : Pollable {}; 

Jishnu knows where to make the change in his drafts. 

End of Annotations:=====
Sender: Chris.Smith@uab.ericsson.se
Message-ID: <389EBE65.3C24229A@uab.ericsson.se>
Date: Mon, 07 Feb 2000 13:45:25 +0100
From: Chris Smith <uabcsru@uab.ericsson.se>
X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.36 i686)
MIME-Version: 1.0
To: issues@omg.org, messaging-rtf@omg.org
Subject: DIIPollable also needs to be an abstract valuetype like
Pollable.
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: fa0!!i?-!!<GTd9\O=e9

Messaging RTF 1.2 adopted a resolution that changes
Pollable from an interface to an abstract valuetype.
DIIPollable inherits from this, and so also needs
to be changed to be a valutype (probably an  abstract 
one).


From: hans.kneubuehl@ubs.com
X-OpenMail-Hops: 2
Date: Fri, 18 Feb 2000 18:56:01 +0100
Message-Id: <H0000340144906bf@MHS>
Subject: Proposed resolution: DIIPollable also needs to be an abstract
valuetype like Pollable.
MIME-Version: 1.0
TO: messaging-rtf@omg.org, uabcsru@uab.ericsson.se
Content-Disposition: inline; filename="BDY.TXT"
	;Creation-Date="Fri, 18 Feb 2000 18:56:01 +0100"
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
	;Creation-Date="Fri, 18 Feb 2000 18:56:01 +0100"
X-UIDL: p"kd9$`"e9#@%!!)jXd9


I agree with Chris and  would like to propose a resolution to this
issue. I 
propose it as changes to orbos/98-05-05, as the draft 1 of the CORBA
Messaging 
Chapter lost hold of DIIPollable!)


- page 119 and page 139, change the following IDL

"interface DIIPollable : Pollable {};"

to

"abstract valuetype DIIPollable : Pollable {};"


- page 120, change

"9.3.4.2 interface DIIPollable
The specific Pollable that indicates interest in DII requests. A
DIIPollable 
can be used
in conjunction with a pollable set to allow a client to block or poll
for the 
completion of
DII requests, similar to the use of
CORBA::ORB::get_next_response. When the
DIIPollable is returned from PollableSet::poll, the reply to some DII
request 
must be
ready for processing."

to

"9.3.4.2 abstract valuetype DIIPollable
The specific Pollable that indicates interest in DII requests. A
DIIPollable 
can be used
in conjunction with a pollable set to allow a client to block or poll
for the 
completion of
DII requests, similar to the use of
CORBA::ORB::get_next_response. When the
DIIPollable is returned from PollableSet::poll, the reply to some DII
request 
must be
ready for processing."


Rational: see below
> -----Original Message-----
> From: uabcsru [mailto:uabcsru@uab.ericsson.se]
> Sent: Monday, February 07, 2000 1:45 PM
> To: issues; messaging-rtf
> Cc: uabcsru
> Subject: UNAUTHENTICATED: DIIPollable also needs to be an abstract
> valuetype like Pollable.
> 
> 
> Messaging RTF 1.2 adopted a resolution that changes
> Pollable from an interface to an abstract valuetype.
> DIIPollable inherits from this, and so also needs
> to be changed to be a valutype (probably an  abstract 
> one).
>