diff options
| author | mk1 <mk1@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 2001-07-25 19:48:50 +0000 |
|---|---|---|
| committer | mk1 <mk1@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 2001-07-25 19:48:50 +0000 |
| commit | c8881bc60361a63aedad34418767734cafd3a662 (patch) | |
| tree | 4ec47f0b16464b3f9435bd6073b0cafef106be65 | |
| parent | b0628a15ffc0c85721c25d9a66de8972572bd476 (diff) | |
| download | ATCD-c8881bc60361a63aedad34418767734cafd3a662.tar.gz | |
ChangeLog: Wed Jul 25 12:50:00 2001 Michael Kircher <Michael.Kircher@mchp.siemens.de>
| -rw-r--r-- | TAO/ChangeLogs/ChangeLog-02a | 10 | ||||
| -rw-r--r-- | TAO/tao/Strategies/DIOP_Factory.cpp | 9 |
2 files changed, 19 insertions, 0 deletions
diff --git a/TAO/ChangeLogs/ChangeLog-02a b/TAO/ChangeLogs/ChangeLog-02a index 61510649ded..3e6b5b78968 100644 --- a/TAO/ChangeLogs/ChangeLog-02a +++ b/TAO/ChangeLogs/ChangeLog-02a @@ -1,3 +1,13 @@ +Wed Jul 25 12:50:00 2001 Michael Kircher <Michael.Kircher@mchp.siemens.de> + + * tao/Strategies/DIOP_Factory.cpp: + + Changed the return value of requires_explicit_endpoint () to 0 + and documented that this return code is not reflecting that + the endpoints are not cleaned-up but that we disable it by default + because DIOP is only suitable for certain use cases, e.g. it only + supports one-ways. + Wed Jul 25 08:41:39 2001 Jeff Parsons <parsons@cs.wustl.edu> * TAO_IDL/be/be_visitor_interface/interface_cs.cpp: diff --git a/TAO/tao/Strategies/DIOP_Factory.cpp b/TAO/tao/Strategies/DIOP_Factory.cpp index 35d93c4b900..70f6828ff07 100644 --- a/TAO/tao/Strategies/DIOP_Factory.cpp +++ b/TAO/tao/Strategies/DIOP_Factory.cpp @@ -74,6 +74,15 @@ TAO_DIOP_Protocol_Factory::make_connector (void) int TAO_DIOP_Protocol_Factory::requires_explicit_endpoint (void) const { + // This switch is actually meant to distinguish between pluggable + // protocols which are able to clean up their endpoints and such + // that aren't. E.g. UIOP will leave files, it therefore returns 1, + // IIOP cleans up its endpoint resources, which therefore return 0. + // + // DIOP does clean up endpoint resources, but as DIOP is only + // suitable for special environments, e.g. it supports only one-ways, + // it returns 1 for an other reason than resource clean-up. + return 1; } |