Free High Performance CORBA Notification Service from AT&T Laboratories

omniORB Home AT&T Research

Older News

• 23-Oct-2003. The final release was postponed because of a deadlock bug.  I did some extensive work to try to make sure there are not more such deadlock bugs, and at the same time I changed all locking code to be safer w.r.t. lock release under exceptional conditions.  I also added support for object garbage collection that will be useful for very long-lived notifid.  (See channel.cfg for details.)  The latest updates have been checked in to the omniNotify2_develop branch.  See this note for how to get it.  It would be great if some people could try out these latest fixes and give me feedback.
  
  
• 6-Aug-2003.  The stuff mentioned below has happened, and we are ready for some people to do final testing and suggest any final patches/fixes, e.g., for building on specific platforms.  The latest omniNotify source depends on the latest omniORB 4 source, so the official omniNotify 2.0 release will happen shortly after the next official omniORB 4 release.  This should happen soon.  In the meantime this note describes how to get the latest of both.



• 18-Jun-2003.  Well it has been about a year and still no official 2.0 release.  The good news is that 2.0.ALPHA has been working fine for many people.  2.0 WILL happen soon.  A few small things need to happen beforehand.  First, Duncan Grisby moved the omniNotify cvsroot to sourceforge.  I decided to wait to make sure that was all set up before I did a 2.0 release from that location.   Second, Duncan is porting omniNotify 2.0 to windows, and it looks like his port is far enough along to make it into the 2.0 release.  Third, there are a couple of known bugs with known fixes that I plan to put in.  So please stay tuned!!
  
  I will announce the new sourceforge info as soon as it is fully set up, and I will announce the 2.0 release sometime not too long after that.



• 23-May-2002.   omniNotify 2.0.ALPHA is now available for those that need to try using omniNotify with omniORB4 as soon as possible. The official omniNotify 2.0 release will not occur until omniORB4 is officially released and until omniNotify 2.0 is fully tested.



• 13-May-2002.   omniNotify version 1.2 released. This is mostly a bug fix release, rolling up all known fixes for 1.1. The ndadmin program is also included; see 28 Feb. announcement.  You can download omniNotify 1.2 now or read the 1.2 release notes.   Please join the omniNotify mailing list to stay informed about future omniNotify developments.
  
  This release was done in part to set up a stable branch point for future development -- omniNotify2.x will branch from this point. omniNotify 1.2 only works with omniORB3 (version 3.0.4 or later). The plan is for omniNotify 2.x to work with both omniORB3 and omniORB4.



• 3-May-2002.   As you may know, the Cambridge UK Lab, original home of all omniORB development, closed on April 25.  Fortunately, it looks like omniORB as a project will live on, and Duncan Grisby will continue to be the lead maintainer.
  
  Please see for ways to support omniORB's continued development.
  
  What this means for omniNotify:   The omniNotify project also lives on!  Since the main developer (Bob Gruber) works in the States for AT&T Labs Research in Florham Park, New Jersey, the closing of the Cambridge lab had less of an impact on omniNotify than on omniORB.  CVS and FTP access for omniNotify files has moved; the download page has been updated to reflect this change.



• 3-May-2002.   Bob Gruber's Current Plans:
  • Get omniNotify working with omniORB4 ASAP
  • Do a new release reflecting these changes and all the latest bug fixes
  • May 25 - Jun 11: Get married, go on honeymoon
    (totally out of contact during this time period :->)
  • Future plans include finally doing the much-delayed port to Win NT/2000.



• 28-Feb-2002.   Bug fixes added to CVS repository and patch file.  See patch and bug list.  In addition to the bug fixes, some simple updates were added:
  
  • There is a new ndadmin program in the examples directory. It supports the same Interactive Mode supported by notifd via the -i option. Thus, you can now start notifd without -i, and at any time start up an ndadmin to interactively control it. Note that 'exit' no longer destroys the server, it simply exits the Interactive Mode. To destroy the server, use 'shutdown'.
  • A new delay param, -M, was added to all the examples. Use -h with any of the example programs for info.



• 9-Oct-2001.  omniNotify 1.1 finally released!  You can download omniNotify 1.1 now or read the 1.1 release notes.  The documentation pages have been updated.
   



• 3 August 2001 - omniNotify 1.1 status:  I am traveling August 3 through August 15th, so I decided to wait on the release until I am around to answer questions.   I will do the 1.1 release after I return.



• 15 Dec 2000 -  BETA version of omniNotify 1.1 is available for those who want to help us put it through its paces.  With your help the official release (early January, 2001) will be more robust.
  
  You can download the 1.1 beta or read the 1.1 release notes.  The documentation pages have been updated to cover the new example programs in the 1.1 release.  Apart from these 3 kinds of pages (1.1 download, 1.1 release notes, and documentation) the rest of this site discusses the 1.0 release.



• 13 Oct 2000 - bug number 2 , reported yesterday, is serious enough to justify a new release of omniNotify. (We were hoping for a 1 week fix but it took us a bit longer !! to produce the 1.1 beta -- next time we'll make a more realistic estimate.)



• 12 Oct 2000 - bug number 1 fixed : you can obtain a patch from the patch & bug list



•   4 Oct 2000 - omniNotify 1.0, the initial release, is available.  You can download the release or read the release notes.