1 Orber Release Notes
1.1 Orber 3.6.6
1.1.1 Improvements and New Features
-
It is now possible to configure incoming connections which
overrides some global configuration parameters. See
orber:add_listen_interface/2/3.
Own Id: OTP-6696 Aux Id:
1.2 Orber 3.6.5
1.2.1 Improvements and New Features
-
Removed some unused code.
Own Id: OTP-6527 Aux Id:
1.3 Orber 3.6.4
1.3.1 Improvements and New Features
-
Orber can now be configured so that different NAT parameters
can be specified for different interfaces.
Own Id: OTP-6165 Aux Id:
-
It is now possible to set the keepalive option for incoming
and outgoing IIOP connections. For more information, see the
Configuration chapter in the User's Guide.
Own Id: OTP-6370 Aux Id: seq10532
-
The new function orber:close_connection/1/2 allows a client
to close connections to an object residing on a remote ORB.
Own Id: OTP-6371 Aux Id: seq10532
-
Orber now use the SSL two-phase accept strategy to avoid
that new incoming connections via SSL are not blocked
by a previous connect attempt that never initiated the
SSL handshake. Note, the configuration parameter
iiop_ssl_accept_timeout should be set (default infinity).
For more information, see the Configuration chapter in the
User's Guide. If Orber is started in secure mode, the
installed SSL version must support ssl:ssl_accept/1/2 and
ssl:transport_accept/1/2.
Own Id: OTP-6372 Aux Id: seq10105
1.3.2 Fixed Bugs and Malfunctions
-
The operation orber_ifr:contents/2 could only handle dk_All.
Own Id: OTP-6385 Aux Id:
1.4 Orber 3.6.3
1.4.1 Improvements and New Features
-
When installing Orber it is now possible to set the priority
for Orber internal Mnesia tables. For more information, see the
Reference Manual regarding orber:install/2.
Own Id: OTP-5907 Aux Id: seq10156
-
The operation corba_object:is_a/2/3 now only connect to a remote
ORB if necessary (i.e. the target object inherits from objects
associated with the given IFR id).
Own Id: OTP-5908
1.4.2 Fixed Bugs and Malfunctions
-
The operation corba_object:is_remote/1 always returned
true, which was introduced in orber-3.2.10.
Own Id: OTP-5909
1.5 Orber 3.6.2
1.5.1 Improvements and New Features
-
Native interceptors may now export new_in_connection and
new_out_connection operations with arity 5. If this is the
case, information about the local interface and port is
passed to the interceptor. Orber's built in interceptors
have been changed to include this information as well.
Own Id: OTP-5671
1.5.2 Fixed Bugs and Malfunctions
-
In some cases, e.g. incorrect GIOP headers or a CancelRequest
containing a non-existing RequestId, the incoming connection
would be terminated.
Own Id: OTP-5672 Aux Id: seq10037
-
If combining the 'Use Current Interface in IOR' and
'Use IPv6' flags, exported IOR:s contained an incorrect
host address.
Own Id: OTP-5673
1.6 Orber 3.6.1
1.6.1 Improvements and New Features
-
Reduced overhead when using outgoing ACL with a local interface
defined.
Own Id: OTP-5659
-
Added guards to ensure that, when so required, a list
of IOP_ServiceContext's is passed instead of, for example,
just the context record.
Own Id: OTP-5660
1.6.2 Fixed Bugs and Malfunctions
-
The documentation referred to two different context definitions,
the incorrect ServiceContext and the correct IOP_ServiceContext.
The hrl file PATH/include/corba.hrl also contained the incorrect
record definition. This has now been updated so that only
IOP_ServiceContext is used and referred to.
Own Id: OTP-5658
1.7 Orber 3.6
1.7.1 Improvements and New Features
-
It is now possible to define a Access Control List (ACL),
which limits the host and ports Orber may connect to or
accept connections from.
Own Id: OTP-5567
-
It is now possible to add, and remove, listen interfaces.
For more information, consult the User's Guide and the
orber module Reference Manual.
Own Id: OTP-5568
-
It is now possible to activate and deactivate Audit/Trail
logging. One of the three built in interceptors will be used
depending on the requested verbosity.
Own Id: OTP-5569
-
It is now possible to configure Orber to add the interface,
to exported local IOR:s, a Request came via.
Own Id: OTP-5570
-
It is now possible to instruct Orber which local interface an outgoing Request
shall be sent via. To accomplish this the Orber generic context must be
added added to each invocation.
Own Id: OTP-5571
-
It is now possible to define a default local interface,
which Orber will use when connecting to another ORB.
Own Id: OTP-5583
For information about older versions see
release notes history.
orber 3.6.6
Copyright © 1991-2007
Ericsson AB