summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorirfan <irfan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2001-07-11 08:11:48 +0000
committerirfan <irfan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2001-07-11 08:11:48 +0000
commita20b2f1e28440942dfc6e39d38abc68a0f9b7a8a (patch)
treef9d06ac9250e72b160d4ef60cd7deb727d64b85e
parentbdf54e8d368334da7b11f0cf375df51f7b1c4152 (diff)
downloadATCD-a20b2f1e28440942dfc6e39d38abc68a0f9b7a8a.tar.gz
*** empty log message ***
-rw-r--r--TAO/ChangeLogs/ChangeLog-02a29
1 files changed, 29 insertions, 0 deletions
diff --git a/TAO/ChangeLogs/ChangeLog-02a b/TAO/ChangeLogs/ChangeLog-02a
index c59f5ca78f4..d92ff2309d9 100644
--- a/TAO/ChangeLogs/ChangeLog-02a
+++ b/TAO/ChangeLogs/ChangeLog-02a
@@ -1,3 +1,32 @@
+Wed Jul 11 02:19:59 2001 Irfan Pyarali <irfan@cs.wustl.edu>
+
+ * tao/RTPortableServer/RT_Servant_Dispatcher.cpp: Remember the
+ native priority of the invoking thread. Once the invocation
+ completes, restore the thread to the original native thread
+ priority.
+
+ Previously, when the priority was restored, it was done it terms
+ of CORBA priority. The problem with this approach was that in
+ the conversion from native to CORBA and then back to native, we
+ can lose precision and hence the native priority of the native
+ thread may not be the same as its original native priority.
+ Therefore, remembering the original native priority will
+ alleviate this problem.
+
+ * tao/Protocols_Hooks:
+ * tao/Default_Protocols_Hooks:
+ * tao/RT_Protocols_Hooks.cpp:
+
+ Expanded the priority interfaces on the Protocols_Hooks such
+ that the user can obtain both the native and CORBA priorities.
+ Also, the user can set both.
+
+ * tao/RTCORBA/RT_Invocation_Endpoint_Selectors.cpp (select_endpoint):
+ * tao/RTCORBA/RT_Current.cpp (the_priority):
+ * tao/Strategies/Reactor_Per_Priority.cpp (reactor):
+
+ Changed to use new priority interfaces.
+
Tue Jul 10 22:37:48 2001 Ossama Othman <ossama@uci.edu>
* orbsvcs/orbsvcs/Security/QOPPolicy.cpp (copy):