Overview
Request 954346 accepted
- update to 4.3.0:
* 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.
* New Connection Info callback to receive information about
connection establishment and errors.
* New plain object keys POA policy, extending the capabilities of
omniINSPOA.
* Support for vast CORBA messages on 64 bit platforms.
* Support for PyPy in omniidl and omniORBpy.
* omniCallDescriptor::current() and omniCallHandle::current() to
access information about the current call on a server.
* The sslContext class is now in the omni namespace.
* The marshalled format of exceptions inside Anys has changed for
compatibility with other ORBs, meaning that it is incompatible
with omniORB versions prior to 4.3. See the exceptionIdInAny
configuration parameter to revert to the previous format.
- Created by StefanBruens
- In state accepted
- Package maintainer: StefanBruens
Request History
StefanBruens created request
- update to 4.3.0:
* 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.
* New Connection Info callback to receive information about
connection establishment and errors.
* New plain object keys POA policy, extending the capabilities of
omniINSPOA.
* Support for vast CORBA messages on 64 bit platforms.
* Support for PyPy in omniidl and omniORBpy.
* omniCallDescriptor::current() and omniCallHandle::current() to
access information about the current call on a server.
* The sslContext class is now in the omni namespace.
* The marshalled format of exceptions inside Anys has changed for
compatibility with other ORBs, meaning that it is incompatible
with omniORB versions prior to 4.3. See the exceptionIdInAny
configuration parameter to revert to the previous format.
StefanBruens accepted request