diff options
author | Johnny Willemsen <jwillemsen@remedy.nl> | 2007-01-08 10:28:45 +0000 |
---|---|---|
committer | Johnny Willemsen <jwillemsen@remedy.nl> | 2007-01-08 10:28:45 +0000 |
commit | dacf9c73711cfc1fd49dbdfefe36927a254d444f (patch) | |
tree | 8e25c9ff8916c77f1a32787445a75aad7b0baf6a | |
parent | f3e5b3ce043d3c0dbf1eefde60506ca83384d8d4 (diff) | |
download | ATCD-dacf9c73711cfc1fd49dbdfefe36927a254d444f.tar.gz |
Mon Jan 8 09:37:30 UTC 2007 Johnny Willemsen <jwillemsen@remedy.nl>
-rw-r--r-- | TAO/NEWS | 37 |
1 files changed, 18 insertions, 19 deletions
@@ -6,7 +6,7 @@ PLANNED MAJOR CHANGES "SOMETIME IN THE FUTURE" (i.e., exact beta not known) . (JTC) autoconf support for tests and examples subdirectories. -PLANNED CHANGES FOR "TAO-5.5.5" +PLANNED CHANGES FOR "TAO-5.5.6" =============================== . (OO) Coverity error fixes for TAO. @@ -14,24 +14,6 @@ PLANNED CHANGES FOR "TAO-5.5.5" mapping requirement). . (OO) Various other fixes that have been piling up. -. (OCI) Contributed the Transport::Current support - an optional - feature with IDL interfaces, which enables users to obtain - information about the Transports used to send or receive a - message. The basic intent is to provide (typically) a - read-only interface to obtaining data like the number of bytes - transferred or the number of messages sent and received. - Since specific Transports may have very different - characteristics, a simple generic implementation for - Transport::Current is insufficient. This implementation also - provides support for specific Transport implementations. See - the TC_IIOP implementation, which is an IIOP-specific - Transport::Current, which extends the generic interface with - operations providing information about IIOP endpoints, like - host and port. To build TAO with support for this feature, a - macro named TAO_HAS_TRANSPORT_CURRENT must be defined and have - a value != 0. For more details of how the feature is intended - to be used, see docs/transport_current/index.html - USER VISIBLE CHANGES BETWEEN TAO-1.5.4 and TAO-1.5.5 ==================================================== @@ -76,6 +58,23 @@ USER VISIBLE CHANGES BETWEEN TAO-1.5.4 and TAO-1.5.5 implementation can utilize a separate ORB for dispatching events to consumers. +. Contributed the Transport::Current support - an optional + feature with IDL interfaces, which enables users to obtain + information about the Transports used to send or receive a + message. The basic intent is to provide (typically) a + read-only interface to obtaining data like the number of bytes + transferred or the number of messages sent and received. + Since specific Transports may have very different + characteristics, a simple generic implementation for + Transport::Current is insufficient. This implementation also + provides support for specific Transport implementations. See + the TC_IIOP implementation, which is an IIOP-specific + Transport::Current, which extends the generic interface with + operations providing information about IIOP endpoints, like + host and port. To build TAO with support for this feature, a + macro named TAO_HAS_TRANSPORT_CURRENT must be defined and have + a value != 0. For more details of how the feature is intended + to be used, see docs/transport_current/index.html USER VISIBLE CHANGES BETWEEN TAO-1.5.3 and TAO-1.5.4 ==================================================== |