Issue 1787:  Current:get_policy() is semanitically insconsitent with  curr. object mode (sec-rev)
Source:  (, )
Nature:  Revision
Severity:  Significant
Summary: Summary: The model currently specifies that _set_policy_overrides(), and 
 get_policy() apply to the particular object reference.
 
 That would mean that the policies applied to accessing Current.
 I suggest that we aliviate this discrepancy by putting a
 CORBA::PolicyManager get_policy_manager() on the Current interface.
 The PolicyManager is currently part of the new Async Messaging Specification
 and would be a good interface to do this with.
 

Resolution: 
Revised Text: 
Actions taken:
August 10, 1998: received issue
June 18, 1999: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <www>
Date: Fri, 7 Aug 1998 18:32:25 -0400
From: www
To: juergen@omg.org, web-incoming@omg.org
Subject: WWW Form output

Name: Polar Humenn
Company: Adiron, LLC
Email: polar@adiron.com
Notification: Yes
Specification: Security 1.2
Section: 15.7.2
Formal #: ????
Version: 1.2 Draft
Revision_Date: 5 Jan 1998
Page: 15-75,76
Nature: Revision
Severity: Significant
full_desc: Current:get_policy() is semanitically insconsitent with the

current object model.

The model currently specifies that _set_policy_overrides(), and 
get_policy() apply to the particular object reference.

That would mean that the policies applied to accessing Current.

Theses functions are sort of doing double duty, in the aspect as
they are ignoring their obligation to the semantics above, and
acting as a policy manager for the thread.

I suggest that we aliviate this discrepancy by putting a
CORBA::PolicyManager get_policy_manager() on the Current interface.
The PolicyManager is currently part of the new Async Messaging
Specification
and would be a good interface to do this with.

The get_policy_manager() operation can be restricted to managing
policies
for the current thread as such with current.
submit: Submit Issue Report