[omniORB] Announce: omniORB 4.1.0 beta 2 and omniORBpy 3.0 beta 2

[Duncan Grisby]

omniORB 4.1.0 beta 2 and omniORBpy 3.0 beta 2 are now available.

With luck, these will be the last beta releases, and the final releases
will be available within a few weeks. Please test the new betas and
report any issues you find, so we can move to the final releases as soon
as possible.

The releases are available from SourceForge as usual:

  http://sourceforge.net/project/showfiles.php?group_id=51138&package_id=44914&release_id=417645
  http://sourceforge.net/project/showfiles.php?group_id=51138&package_id=48639&release_id=417647

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/


Changes since omniORB 4.1.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         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --