Duncan Grisby
2006-09-29 04:17:08 UTC
omniORB 4.1.0 RC 1 and omniORBpy 3.0 RC 1 are now available. Please test
these release candidates.
The releases are available from SourceForge as usual:
http://sourceforge.net/project/showfiles.php?group_id=51138&package_id=44914&release_id=450879
http://sourceforge.net/project/showfiles.php?group_id=51138&package_id=48639&release_id=450880
Binaries are not available at this stage.
Documentation is included in the distributions, or can be read online
here:
http://omniorb.sourceforge.net/omni41/omniORB/
http://omniorb.sourceforge.net/omnipy3/omniORBpy/
These are major new releases over omniORB 4.0.x and omniORBpy 2.x. A
summary of the new features:
Changes since omniORB 4.1.0 beta 2 and omniORBpy 3.0 beta 2
-----------------------------------------------------------
- Incompatible change to the clientSendRequest interceptor members.
Application code using the interceptor will require a small
modification.
- Support for insertion / extraction of various types from standard
iostreams.
- More comprehensive logging of connection and protocol errors.
- Experimental omniConnectionMgmt extension.
- New omniORBpy C++ api functions.
- omniORBpy support for Python 2.5.
- Minor bug fixes.
Changes since omniORB 4.1.0 beta 1 and omniORBpy 3.0 beta 1
-----------------------------------------------------------
- IPv6 support.
See section 8.6.1 of the omniORB manual for details.
- New endPointPublish parameter.
Used for configuring what to publish in IORs. See section 8.6.2
of the omniORB manual.
- Minor bug fixes.
Changes since omniORB 4.0.x
---------------------------
- Objects by value support.
omniORB now supports the full objects by value specification, with
the exception of custom valuetypes. See chapter 13 of the omniORB
manual / chapter 10 of the omniORBpy manual for information about
valuetype in omniORB.
- Abstract interfaces support.
- New simpler and more efficient C++ Any implementation.
- New socket collection implementation.
Uses poll() on platforms where it is available to avoid limiting
the number of connections to FD_SETSIZE. Windows specific version
that better manages the unusual Windows fd_set.
- New tracing options traceTime and traceInvocationReturns.
See section 4.2 of the omniORB manual.
- C++ mapping updated to version 1.1.
Deprecation of RefCountServantBase; Servant_var template type.
- Support for local interfaces in C++.
In particular, ServantManagers and AdapterActivators no longer
need to be activated in a POA, but can be simple C++ objects. See
the examples in src/examples/poa/servant_manager.
- Partial support for local interfaces in Python.
In particular, ServantManagers and AdapterActivators no longer
need to be activated in a POA, but can be simple Python objects.
See the examples in examples/poa.
- New-style Python classes can now be used for servants.
Enjoy!
Duncan.
these release candidates.
The releases are available from SourceForge as usual:
http://sourceforge.net/project/showfiles.php?group_id=51138&package_id=44914&release_id=450879
http://sourceforge.net/project/showfiles.php?group_id=51138&package_id=48639&release_id=450880
Binaries are not available at this stage.
Documentation is included in the distributions, or can be read online
here:
http://omniorb.sourceforge.net/omni41/omniORB/
http://omniorb.sourceforge.net/omnipy3/omniORBpy/
These are major new releases over omniORB 4.0.x and omniORBpy 2.x. A
summary of the new features:
Changes since omniORB 4.1.0 beta 2 and omniORBpy 3.0 beta 2
-----------------------------------------------------------
- Incompatible change to the clientSendRequest interceptor members.
Application code using the interceptor will require a small
modification.
- Support for insertion / extraction of various types from standard
iostreams.
- More comprehensive logging of connection and protocol errors.
- Experimental omniConnectionMgmt extension.
- New omniORBpy C++ api functions.
- omniORBpy support for Python 2.5.
- Minor bug fixes.
Changes since omniORB 4.1.0 beta 1 and omniORBpy 3.0 beta 1
-----------------------------------------------------------
- IPv6 support.
See section 8.6.1 of the omniORB manual for details.
- New endPointPublish parameter.
Used for configuring what to publish in IORs. See section 8.6.2
of the omniORB manual.
- Minor bug fixes.
Changes since omniORB 4.0.x
---------------------------
- Objects by value support.
omniORB now supports the full objects by value specification, with
the exception of custom valuetypes. See chapter 13 of the omniORB
manual / chapter 10 of the omniORBpy manual for information about
valuetype in omniORB.
- Abstract interfaces support.
- New simpler and more efficient C++ Any implementation.
- New socket collection implementation.
Uses poll() on platforms where it is available to avoid limiting
the number of connections to FD_SETSIZE. Windows specific version
that better manages the unusual Windows fd_set.
- New tracing options traceTime and traceInvocationReturns.
See section 4.2 of the omniORB manual.
- C++ mapping updated to version 1.1.
Deprecation of RefCountServantBase; Servant_var template type.
- Support for local interfaces in C++.
In particular, ServantManagers and AdapterActivators no longer
need to be activated in a POA, but can be simple C++ objects. See
the examples in src/examples/poa/servant_manager.
- Partial support for local interfaces in Python.
In particular, ServantManagers and AdapterActivators no longer
need to be activated in a POA, but can be simple Python objects.
See the examples in examples/poa.
- New-style Python classes can now be used for servants.
Enjoy!
Duncan.
--
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --