[omniORB] New features: omniORB and omniORBpy 4.3.0 beta 1

[Duncan Grisby]

Hot on the heels of the very boring 4.2.3 releases, something much more
interesting...

omniORB and omniORB 4.3.0 beta 1 are now available. These contain new
features. Although they are beta releases, they are in production use
in at least one large scale application, so they are quite stable.

Get them here:

https://sourceforge.net/projects/omniorb/files/omniORB/omniORB-4.3.0/
https://sourceforge.net/projects/omniorb/files/omniORBpy/omniORBpy-4.3.0/

Or do an svn checkout of the 4_3 branch.

Highlights of the changes:

 - A new omniORB-specific HTTP / HTTPS transport, with a number of
   capabilities:

    . Full encapsulation of GIOP messages in HTTP.

    . Support for web proxies, transparent web proxies, reverse
      proxies.

    . For cases where security is important but an end-to-end HTTPS
      connection cannot be assured, support for in-message encryption.

 - Support for vast CORBA messages on 64 bit platforms.

 - Support for PyPy in omniidl and omniORBpy.

 - omniCallDescriptor::current() and omniCallHandle::current() (in C++)
   and omniORB.currentCallInfo() (in Python), to access information
   about the current call on a server.


Enjoy!

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --