(17 August 2010) We are pleased to announce the release of OpenDDS version 2.2!

• Completed the implementation of the Content-Subscription Profile (which was begun in version 1.3 of OpenDDS). This includes:
  • QueryCondition (previously OpenDDS had a partial implementation)
  • ContentFilteredTopic
  • MultiTopic
  The content-subscription profile can be disabled at compile-time in order to reduce footprint: set the MPC feature “content_subscription” to 0.
• The code generation tools for OpenDDS have changed in this release. The Perl script “dcps_ts.pl” is no longer used and instead the OpenDDS IDL Compiler “opendds_idl” takes its place. opendds_idl also includes the functionality which used to be in tao_idl and enabled with -Gdcps. Existing applications that use MPC do not need to make any changes unless they happen to depend on some rarely-used arguments to dcps_ts.pl. See the OpenDDS Developer’s Guide for the list of arguments accepted by opendds_idl.
• Renamed odds_repoctl command to repoctl. Add a decorator if needed when installing external to the OpenDDS directories.
• Renamed odds_monitor command to monitor. Add a decorator if needed when installing external to the OpenDDS directories.
• Renamed Wireshark dissector ‘odds’ library to ‘OpenDDS_Dissector’. The source directory was renamed from $DDS_ROOT/tools/odds_dissector to $DDS_ROOT/tools/dissector.
• Fixed transport so it now allows associations between datareaders and datawriters attached to the same transport to work.
• Fixed a bug that causes samples larger than 64K to not work correctly with the SimpleTCP transport.
• Added nak_delay_intervals and nak_max configuration options for reliable multicast to help reduce naks.
• Added support for Ownership qos.
• Added support for GROUP presentation.
• Changed the default DataWriterQos reliability max_blocking_time from infinite to be 100ms to be consistent with spec 1.2.
• A new “configure” script is available to assist with setting up prerequisites for OpenDDS compilation, including optionally downloading ACE+TAO. See the INSTALL file for details.

See the Release Notes for details.

(18 June 2010) We are pleased to announce the release of OpenDDS version 2.1.3!

• Various fixes for memory management issue on transport framework.
• Fixed duplicate message issue caused by a lost link.
• Memory leak fixes.
• Fixed deadlocks on reliable multicast transport during association and shutdown periods.
• Improved reliable multicast transport and reduced nak overflow.
• Extended the capabilities of the OpenDDS-Bench performance test framework. This consists mostly of expanded pre-configured tests as well as additional execution and plotting scripts. The user guide at performance-tests/Bench/doc/user_guide.html contains the details.
• Masked interrupts in threads created by OpenDDS to avoid failures while in system calls. Example:
  
  ERROR: ACE::handle_write_ready return -1 while waiting to unclog. handle_write_ready: Interrupted system call
  
  
• Added support to set the TTL for multicast transports.

See the Release Notes for details.

Should IBM consider a return of OS/2? A systems integrator close to the computing giant swears there’s a move afoot inside IBM to reintroduce the operating system — revered by some, reviled by many –before it faded out more than 10 years ago. He has heard this from inside Big Blue itself.

This will mean nothing to young’uns who do not remember the great OS war waged between IBM and Microsoft after their joint development of OS/2 fell apart. Running on both PCs and servers, OS/2 was object-oriented and CORBA-compliant, could multitask and sported a neat graphical user interface. People liked the OO Workplace Shell GUI very much.

…

According to the integrator, IBM’s nascent plan is to repurpose OS/2 “services” atop a Linux core.

The obvious question is why? And the answer is despite Windows’ spanking, IBM shops still run quite a bit of OS/2 — not that they’ve advertised that fact. In theory these companies can drop this Linux-OS/2 amalgam in to replace aging installations with minimal disruption.

I thought Workplace Shell was the best thing about OS/2, otherwise my interest in OS/2 at this point is pretty minimal.

(23 March 2010) We are pleased to announce the release of OpenDDS version 2.1.2!

• This is a bugfix release to account for issues introduced by the previous version.
• Various bugfixes for locking issues during sample removal.
• Fixed a bug in obtain_buffer() that did not return the TIMEOUT error code when max_blocking_time is 0 or a very small period.
• Fixed a deadlock in the new IP multicast transport caused when data is received while a reliable session is handshaking.
• Fixed an issue which caused spurious synch threads to be created for connectionless transports (i.e. UDP/IP, IP multicast).
• Enhanced the experimental UDP/IP transport to support multiplexing samples to unique endpoints rather than unique entities.

See the Release Notes for details.

(8 March 2010) We are pleased to announce the release of OpenDDS version 2.1.1!

• This is a bugfix release to account for issues introduced by the previous version.
• Various bugfixes have been applied to the new IP multicast transport and the Extensible Transport Framework (ETF) to improve stability.
• Added IDL for ContentFilteredTopic and MultiTopic, but they are not yet implemented (operations will return NULL or RETCODE_UNSUPPORTED).
• A Wireshark 1.2.x compatible dissector is included in this release. See $DDS_ROOT/tools/odds_dissector/README for details.

See the Release Notes for details.

(5 February 2010) We are pleased to announce the release of OpenDDS version 2.1!

• The OpenDDS-Bench performance testing framework has been enhanced to include support for user-submitted performance results.
• A new monitor library introduces an instrumentation mechanism for reporting OpenDDS runtime information.
• A new instrumentation application is available to view executing OpenDDS service Entities.
• A new IP multicast transport is available which replaces the older ReliableMulticast and SimpleMcast transports.
• A new UDP/IP transport is available which replaces the older SimpleUdp transport.
• Numerous bugs in the Extensible Transport Framework (ETF) have been addressed to improve the stability of new and existing transports.

See the Release Notes for details.