summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorirfan <irfan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2000-03-25 09:24:26 +0000
committerirfan <irfan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2000-03-25 09:24:26 +0000
commitd78c3ca699319432aa502903925859b86c8a20c5 (patch)
treef348e719254b6c1107b27b08c3fb8a1982eaebe2
parentcc52928075c1a1f6e2ba3b1dba3c04596efba2bd (diff)
downloadATCD-d78c3ca699319432aa502903925859b86c8a20c5.tar.gz
Add comments to explain the reference count in the
TAO_SHMIOP_Server_Connection_Handler.
-rw-r--r--TAO/tao/SHMIOP_Connect.h9
1 files changed, 6 insertions, 3 deletions
diff --git a/TAO/tao/SHMIOP_Connect.h b/TAO/tao/SHMIOP_Connect.h
index 1997a730bcd..416cd0bb94d 100644
--- a/TAO/tao/SHMIOP_Connect.h
+++ b/TAO/tao/SHMIOP_Connect.h
@@ -105,7 +105,7 @@ protected:
TAO_ORB_Core *orb_core_;
// Cached ORB Core.
-
+
CORBA::Boolean lite_flag_;
// Are we using lite?
};
@@ -179,8 +179,11 @@ protected:
// Cached tss resources of the ORB that activated this object.
u_long refcount_;
- // Reference count, to avoid early deletes...
-
+ // Reference count. It is used to count nested upcalls on this
+ // svc_handler i.e., the connection can close during nested upcalls,
+ // you should not delete the svc_handler until the stack unwinds
+ // from the nested upcalls.
+
CORBA::Boolean lite_flag_;
// Should we use GIOP or GIOPlite
};