Issue 9735: Section: 8.6 Derivation of RequestInfo (qos4ccm-ftf)
Source: Fraunhofer FOKUS (Mr. Tom Ritter, ritter(at)fokus.fraunhofer.de)
Nature: Revision
Severity: Minor
Summary: Derivation of RequestInfo Why isn't ContainerClientRequestInfo simply derived (with no extension) from PortableInterceptor::ClientRequestInfo? This would save a step (calling request_info()) in user code. Why isn't ContainerServerRequestInfo simply derived (with no extension) from PortableInterceptor::ServerRequestInfo? This would save a step (calling request_info()) in user code.

Resolution: 
Revised Text: 
Actions taken:
May 18, 2006: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 18 May 2006 04:06:58 -0400
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Tom Ritter
Company: Fraunhofer FOKUS
mailFrom: ritter@fokus.fraunhofer.de
Notification: Yes
Specification: QoS4CCM
Section: 8.6
FormalNumber: ptc/06-04-15
Version: 1.0
RevisionDate: April/2006
Page: 28 pp.
Nature: Revision
Severity: Minor
HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3
Description
Derivation of RequestInfo Why isn't ContainerClientRequestInfo simply derived (with no extension) from PortableInterceptor::ClientRequestInfo? This would save a step (calling request_info()) in user code. Why isn't ContainerServerRequestInfo simply derived (with no extension) from PortableInterceptor::ServerRequestInfo? This would save a step (calling request_info()) in user code.