Legacy Issue Number: 3363
Source: Thematix Partners LLC ( Jishnu Mukerji [X] (Inactive))
While editing the changes from the Firewall RTF into Core Chapter 15 I noticed a
curious thing in the Firewall RTF report. It seems that the RTF chose to re-use
a PolicyType id for a new and different policy while obsoleting a published one.
The PolicyType Id in question is 37, which used to be BIDIRECTIONAL_POLICY_TYPE
associated with the structure BiDirPolicy::BidirectionalPolicy
and is now proposed to be BIDIRECTIONAL_INVOKE_POLICY associated with structure
This appears to me to be a dangerous practice, since the fact that the published
standard may have been implemented by someone using the obsolete definition.
I would like to suggest that the recommendation of the Firewall RTF be modified
leaving the published policy type and policy as is with a note stating that it
is obsolete, and a new policy type id be allocated for
Reported: CORBA 2.3.1 — Fri, 25 Feb 2000 05:00 GMT
Disposition: Deferred — CORBA 3.4
This proposal was generated automatically by request of the Task Force Chair Adam Mitz.
Updated: Mon, 30 Mar 2020 19:47 GMT