--------------------------------------------------------------------
1.2.3

  new features
    - IvyClient now implements the directMessage function of the Ivy Protocol.
    - Probe now allows users to send a direct message with the ".direct" command
    - the environment variable IVYBUS is propagated to the children
  doc
    - now includes a simple documentation for IvyDaemon (sgml and readme)
    - README rewritten
  tests
    - I added a regression test to check the API ( java TestApi in the tests
    directory )
    - I added the early disconnexion test ( probe < /dev/null )
  bugfix
    - IvyClient doesn't loop any more in certain conditions of remote
    disconnexion this closes the new bugreport jan/2002
    - early disconnexion is now possible ( java fr.dgac.ivy.Probe < /dev/null), 

------------------------------------------------------------------------------
1.2.2

  bugfix
    IvyClient.java didn't handle the readline()=null correctly. Thus, the
    thread kept on eating CPU when a remote client left the bus.
    This closes Damien Figarol bugreport dec/2002
  bugfix
    The ivy java library wasn't supported on 1.1.x platforms, because of
    missing methods ( java.util.Vector.add(Object) and
    System.setProperty(String,String) ). I switched back to the old API.
    This closes Philippe Truillet bugreport dec/2002.
  cleanup
    examples have been a bit rewritten

------------------------------------------------------------------------------
1.2.1

  bugfix
    Ivy.java Ivy.start(null) now starts on DEFAULT_DOMAIN (Alexandre Lemort),
      the new getDomains(String) outputs the list of domains
    IvyWatcher now empties the datagram buffer with 0x10, thus fixing a nasty
      bug that involved a java client on  windows XP

  Probe
    now displays the real address of the starting domain
    now has a .bind and .unbind commands

------------------------------------------------------------------------------
1.2.0

 bugfix:
   IvyClient if a remote client disconnect brutally ( broken pipe ), the BufferedReader
   takes time to propagate the IOException. It means we are not aware of the
   problem before 2 or 3 messages ( Alexandre Lemort )
   there is a fix in IvyClient, but this is part of the TCP protocol. I will
   receive the timeout when I try to write on the client. To circumvent this, I
   have implemented an extention in the Ivy protocol with 2 new messages, Ping
   and Pong. This is Ivy-java only, and and experimental feature.

 Probe
   Probe can now send empty strings on keyboard input
   rewritten with a looping thread on stdin to allow a cleaner exit on die
     message : not very good
   processes .help, .die , .quit and .bye commands
   it is possible to rename the JPROBE on the bus with the -n switch, it can
     circumvent name collisions during tests
     e.g: java fr.dgac.ivy.Probe -n JPROBE2

 Ivy
   setSoTimeout is back on the server socket
   added a regression test main()
   clients is now a Hashtable. the deletion now works better
   getIvyClientsByName allows the research of IvyClient by name
   getDomain doesnt throw IvyException anymore
   removed the close() disconnect(IvyClient c). Fixes a big badaboum bug
   getDomain becomes public
   adding the sendToSelf feature
   fixed the printStackTrace upon closing of the ServerSocket after a close()

 IvyException changed default access constructor to public access

 IvyApplicationAdapter missed an id in the parameters

 IvyClient
   sendDie() methode goes public
   sendBuffer update with silent error on a broken pipe, unless IVY_DEBUG is set
   the IvyClient gets removed from the list of clients if there is a broken pipe.
   Another bug fixed !
   implements ping and pong protocol
   appName visibility changed from private to protected

 IvyDaemon is granted a public access on its constructor

------------------------------------------------------------------------------
1.0.11 mer jun  5 11:33:16 CEST 2002

 Just a debian package change. No java modification per se.

------------------------------------------------------------------------------
1.0.10 mar jun  4 19:00:32 CEST 2002

TestIvy:
  System.exit on bus die

IvyWatcher
  isInDomain() is wrong  in multicast. I've removed it -> TO FIX
  there was a remanence effect in the datagrampacket buffer. I clean it up after each message
  cleaned up the getDomain() and getPort() code 
  I allow multiple domains
  I Removed the CPU eating loop on soTimeOut, with a vector of broadcast listeners

Probe
  System.exit upon die message

jar file:
  added gnu/regexp and gnu/getopt class files withing the jar file

------------------------------------------------------------------------------
1.0.8

  Fixed a bug in inserted in 1.0.7, added the Counter program,
  useful if you want to have an inexact idea of the number of messages
  circulating on the bus itself.

------------------------------------------------------------------------------
1.0.7

  Fixed a bug in Ivy.java and IvyClient.java, causing the
  problematic 'a(.*) (.*)' matching 'a 2' loosing the first empty matches.
  Beware, this has a cost on effectiveness, but, hey, Ivy-java is not
  optimized at all

------------------------------------------------------------------------------
1.0.6

  Fixed a bug in fr.dgac.ivy.Probe, which didn't use the IVYBUS
  property.

------------------------------------------------------------------------------
1.0.5

  Multicast support

------------------------------------------------------------------------------

  epoch