summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorirfan <irfan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2000-03-25 09:22:31 +0000
committerirfan <irfan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2000-03-25 09:22:31 +0000
commit74a26493e1a13b0d60f285893682db44a0eb6e5a (patch)
tree90b861ed59c20857c04734a8b32875d55a04d73a
parent870138274f496ed52f49c3abc6896cddc008b5ad (diff)
downloadATCD-74a26493e1a13b0d60f285893682db44a0eb6e5a.tar.gz
Add comments to explain the reference count in the
TAO_IIOP_Server_Connection_Handler.
-rw-r--r--TAO/tao/IIOP_Connect.h9
1 files changed, 6 insertions, 3 deletions
diff --git a/TAO/tao/IIOP_Connect.h b/TAO/tao/IIOP_Connect.h
index 3d0509a8fb5..8cec46afd1e 100644
--- a/TAO/tao/IIOP_Connect.h
+++ b/TAO/tao/IIOP_Connect.h
@@ -107,7 +107,7 @@ protected:
TAO_ORB_Core *orb_core_;
// Cached ORB Core.
-
+
CORBA::Boolean lite_flag_;
// Are we using GIOP lite?
};
@@ -181,8 +181,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
};