préparation à la 1.2.3 "promenons nous dans les bois"

5 files changed, 110 insertions, 66 deletions

diff --git a/BUGS b/BUGS
index 173211c..db1d6fc 100644
--- a/BUGS
+++ b/BUGS
@@ -5,12 +5,15 @@ TODO List:
     try echo "coucou" | ivyprobe ... -> use IvyDaemon instead
   * document the extension to the API
   * document the IVY_PING feature
-  * mêmes commandes que sous perl et C.
+  * use the same commands and switches for Probe as in the C ivyprobe 
   * write a domain checker
+  * implement the direct Messages in Probe
 
 -------------------------------------------------------------------------------------
 Known bugs:
 
+  -> i'm writing a testbench for the Api ( TestAPI ) . In progress.
+
 -------------------------------------------------------------------------------------
 Fixed:
 
@@ -70,15 +73,25 @@ Not a bug ?
   sending messages. Try adding an IvyApplicationListener with a callback on
   connect(IvyClient) to trigger the launching of messages
 
+  lun jan  6 16:12:11 CET 2003 (Yannick)
+  If you bind to a Start message after invoking the Ivy.start() method, it is
+  possible that you will miss the start. Be sure to check that all static bindMsg()
+  are done before the start, in order not to miss a message.
+  This is *especially* true when writing benchMarks
+
   bus domain shortcuts ( 10:3456 instead of 10.255.255.255:3456  ) doesnt work
   for UDP broadcast on my development environment. It's okay in multicast (Yannick Jestin)
   In fact, it's a matter of network topography, not of shortcut processing.
 
 
   Using the regression tests on the following platforms:
-      - Solaris: I've got a problem to make it run on the default local Domain
-        (127:2010). But this is not limited to the java ivy port !
-	success with jdk1.1.7A, on jdk1.2 , j2sdk1.3 and 1.4 with a multicast domain or a valid
-	UDP broadcast domain . I guess it's a routing problem once again :-\
-      - GNU/linux: ok with jdk1.3 and jdk1.4
-      - windows:  I don't know how to write tests
+  - Solaris: I've got a problem to make it run on the default local Domain
+  (127:2010). But this is not limited to the java ivy port !
+  success with jdk1.1.7A, on jdk1.2 , j2sdk1.3 and 1.4 with a multicast domain or a valid
+  UDP broadcast domain . I guess it's a routing problem once again :-\
+  - GNU/linux: ok with jdk1.3 and jdk1.4
+  - windows:  I don't know how to write tests
+
+  lun jan  6 16:13:30 CET 2003 (Yannick)
+  disconnect() is not called when we send a "die" command to the remote IvyClient
+  It is normal. disconnect is called when we are issued a die command.
diff --git a/Changelog b/Changelog
index 8941c10..f9d9e50 100644
--- a/Changelog
+++ b/Changelog
@@ -1,4 +1,23 @@
-----------------------------------------------------------------------------------------
+--------------------------------------------------------------------
+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
@@ -13,7 +32,7 @@
   cleanup
     examples have been a bit rewritten
 
-----------------------------------------------------------------------------------------
+------------------------------------------------------------------------------
 1.2.1
 
   bugfix
@@ -26,7 +45,7 @@
     now displays the real address of the starting domain
     now has a .bind and .unbind commands
 
-----------------------------------------------------------------------------------------
+------------------------------------------------------------------------------
 1.2.0
 
  bugfix:
@@ -72,12 +91,12 @@
 
  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:
@@ -96,14 +115,14 @@ Probe
 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
@@ -111,18 +130,18 @@ jar file:
   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
 
diff --git a/Makefile b/Makefile
index 700a7fc..1fc4b42 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,5 @@
 # Be sure to set this before compiling ...
-      VER = 1.2.2
+      VER = 1.2.3
      DIST = lib/ivy-java-$(VER).jar 
      DOCS = doc/html/api
 
diff --git a/README b/README
index 674413e..d5af1c2 100644
--- a/README
+++ b/README
@@ -1,75 +1,87 @@
-ivy-java README
------------------
+			    
+                            ivy-java README
 
-This is open source software distributed under the terms of the GNU
-Lesser General Public License.  See the COPYING.LIB file for details.
-Some included utilities are distributed under the terms of the GNU
-General Public License, a copy of which is included in the file COPYING.
+Last modificiation, lun jan  6 16:25:35 CET 2003 , Yannick
+-----------------------------------------------------------------------------
 
-This page has been hugely inspired from the one Wes wrote for the gnu-regexp
-package. As I am a newbie in package creation, I start from an existing one.
+  Ivy java is open source software distributed under the terms of the GNU
+  Lesser General Public License (LGPL).  See the COPYING.LIB file for details.
+  Some included utilities are distributed under the terms of the GNU
+  General Public License, a copy of which is included in the file COPYING.
+
+  This page has been hugely inspired from the one Wes wrote for the gnu-regexp
+  package. As I am a newbie in package creation, I started from an existing one.
 
 INSTALLING
 
-Copy the ivy-java jar file (located in the 'lib' directory)
-to your usual installation directory for Java archives.
+  Copy the ivy-java jar file (located in the 'lib' directory)
+  to your usual installation directory for Java archives. If it is located in
+  your main java class repository, it is possible that will just work as is,
+  however, you might want to put it elsewhere and fiddle with the CLASSPATH
+  environment variable.
 
-To use ivy-java, you will need to include it in your classpath
-setting.  Typically this is done by adding an entry to your CLASSPATH
-variable setting with the full path to the JAR file, e.g.
+  Typically this is done by adding an entry to your CLASSPATH
+  variable setting with the full path to the JAR file, e.g.
   csh:  % setenv CLASSPATH ${CLASSPATH}:/usr/java/lib/ivy-java.jar
- bash:  % export CLASSPATH=${CLASSPATH}:/usr/java/lib/ivy-java.jar
+  bash:  % export CLASSPATH=${CLASSPATH}:/usr/java/lib/ivy-java.jar
   DOS:  > set CLASSPATH %CLASSPATH%;C:\Java\lib\ivy-java.jar
-Various shells and operating systems may have slightly different methods.
-Consult your Java virtual machine documentation for details.  You may also
-specify the -classpath option to the java executable, e.g.
-compile: % javac -classpath /usr/java/lib/ivy-java.jar MyClass.java
-execute: % java -classpath /usr/java/lib/ivy-java.jar MyClass
+  Various shells and operating systems may have slightly different methods.
+  Consult your Java virtual machine documentation for details.  You may also
+  specify the -classpath option to the java executable, e.g.
+  compile: % javac -classpath /usr/java/lib/ivy-java.jar MyClass.java
+  execute: % java -classpath /usr/java/lib/ivy-java.jar MyClass
 
 DOCUMENTATION
 
-HTML documentation will be provided in the 'doc' directory.  This is basically
-a snapshot of the official ivy-java web site (see below for URL).  The
-documentation files are:
- doc/ivy-java.1  -- man page
- doc/html/api/*.html -- javadoc generated info
+  ivy-java should come with
+  - one man page: doc/ivy-java.1,
+  - the javadoc api html documentation tree: doc/api/
+  - a programmer's guide both in html: doc/programmersguide/ 
+    and in pdf format: doc/programmersguide.pdf 
+
+  If any of those file is missing, see the tar.gz archive on the Ivy java
+  web page ( http://www.tls.cena.fr/products/ivy/ivy-java.html )
 
 UTILITIES
 
-ivy-java comes with a simple utility program intended to test
-and demonstrate its features. It is compiled into the Java archive
-file. To run fr.dgac.ivy.Probe, you will need gnu.regexp and gnu.getopt,
-which are available at http://www.urbanophile.com/~arenn/hacking/download.html, and put those class files in your classpath as well. 
+  ivy-java comes with a simple utility program intended to test
+  and demonstrate its features. It is compiled into the Java archive
+  file. To run fr.dgac.ivy.Probe, you will need gnu.regexp and gnu.getopt,
+  which are available at http://www.urbanophile.com/~arenn/hacking/download.html,
+  and put those class files in your classpath as well. 
 
-There is also a couple of simple graphical utilities akin to Probe ( TestIvy
-and TestIvySwing ). You can try them as well
+  Running java fr.dgac.ivy.Probe successfully is the key to knowing whether
+  your ivy-java installation is OK.
 
+  Ivy also comes with a simple TCP relay, allowing any script application to
+  send text messages onto an Ivy bus. To run the relay, launch
+  $ java fr.dgac.ivy.IvyDaemon
+  Then any line sent to the local port 3456 will be forwarded as an ivy
+  message. It can be used in shell scripts in conjunction with netcat
+  $ echo "hello world" | nc -q 0 localhost 3456
 
 HACKING
 
-You are free to fold, spindle, mutilate and modify this library,
-provided you follow the terms outlined in COPYING.LIB.  The ivy-java
-project team gratefully accepts any bug fixes or enhancements you may
-come up with (see the TODO file if you're in need of some ideas). A
-few parameters at the top of the Makefile in the 'src' directory
-need to be edited to match your local system setup.
+  You are free to fold, spindle, mutilate and modify this library,
+  provided you follow the terms outlined in COPYING.LIB.  The ivy-java
+  project team gratefully accepts any bug fixes or enhancements you may
+  come up with (see the TODO file if you're in need of some ideas). A
+  few parameters at the top of the Makefile in the 'src' directory
+  need to be edited to match your local system setup.
 
 BUG REPORTS
 
-Send bug reports to <jestin@cena.fr>, or join the ivy mailing list
-by sending a "subscribe" message to <ivy-request@tls.cena.fr>.  It helps
-if you can send a code sample showing the messages you were
-using and how you were using it.
+  Send bug reports to <jestin@cena.fr>, or join the ivy mailing list
+  by sending a "subscribe" message to <ivy-request@tls.cena.fr>.  It helps
+  if you can send a code sample showing the messages you were
+  using and how you were using it.
 
 LATEST VERSION
 
-You can always obtain info about the latest version of ivy-java at
-http://www.tls.cena.fr/products/ivy/download/desc/ivy-java.html
-
-New versions are also announced on the ivy mailing list (see above).
-From time to time, upstream source are put on
-http://www.tls.cena.fr/~jestin/ivy-java.html.
+  You can always obtain info about the latest version of ivy-java at
+  http://www.tls.cena.fr/products/ivy/download/desc/ivy-java.html
 
 Thanks!
 
-Yannick Jestin <jestin@cena.fr>
+-- 
+  Yannick Jestin <jestin@cena.fr>
diff --git a/manifest b/manifest
index 29427ea..8480b37 100644
--- a/manifest
+++ b/manifest
@@ -1,3 +1,3 @@
-Manifest-Version: 1.2.1
+Manifest-Version: 1.2.3
 Main-Class: fr.dgac.ivy.Probe
 Created-By: 1.2 (Sun Microsystems Inc.)