aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjestin2004-07-27 16:20:05 +0000
committerjestin2004-07-27 16:20:05 +0000
commitdbfd0856406b93d34d2b9a4b72512ef38b81970b (patch)
treee82b99df4bbe954cd84218e9d0174a942808e851
parent64c95fd653177361f7e691ab345ed54d42ef6aed (diff)
downloadivy-java-dbfd0856406b93d34d2b9a4b72512ef38b81970b.zip
ivy-java-dbfd0856406b93d34d2b9a4b72512ef38b81970b.tar.gz
ivy-java-dbfd0856406b93d34d2b9a4b72512ef38b81970b.tar.bz2
ivy-java-dbfd0856406b93d34d2b9a4b72512ef38b81970b.tar.xz
not bugs, but todo item disappeared.
changelog has been made up-to-date
-rw-r--r--BUGS42
-rw-r--r--Changelog66
-rw-r--r--Makefile18
-rw-r--r--README7
4 files changed, 115 insertions, 18 deletions
diff --git a/BUGS b/BUGS
index 5caadf1..be7f232 100644
--- a/BUGS
+++ b/BUGS
@@ -1,13 +1,13 @@
-------------------------------------------------------------------------------------
-TODO List:
+Won't do list:
+ * implement an interface allowing different regexps implementations, since
+ it exists in jdk 1.4.1 !, while keeping in mind the platform compatibility
+ -> nooooo ( jakarta regexps now )
+-------------------------------------------------------------------------------------
- * ivyprobe is a bit touchy about being fed somethin on standard input
- try echo "coucou" | ivyprobe ... -> use IvyDaemon instead
- * document the extension to the API
- * document the IVY_PING feature
- * use the same commands and switches for Probe as in the C ivyprobe
- * write a domain checker
- * implement the direct Messages in Probe
+TODO List:
+ * try the "many threads option" for sending messages
+ * make a ssh tunnel
-------------------------------------------------------------------------------------
Known bugs:
@@ -52,6 +52,29 @@ réf: [BUGXY]
-------------------------------------------------------------------------------------
Fixed:
+1.2.4
+
+ réf: [BUG J007] incorrect handling of faulty remote Ivy agents
+ for exemple, bad UDP broadcasts, or wrong regexps.
+
+ réf: [BUG J006]
+ * incorrect notification of agent departure
+ $ java -DIVY_DEBUG fr.dgac.ivy.Probe
+ $ ivyprobe
+ and ^C the ivyprobe results in :
+ IVYPROBE connected
+ -->IvyClient JPROBE:IVYPROBE<-- readline null ! leaving the thead
+ -->IvyClient JPROBE:IVYPROBE<-- normally Disconnected from IVYPROBE
+ -->IvyClient JPROBE:IVYPROBE<-- Thread stopped
+ The 1.2.4 releases produces a IVYPROBE disconnected
+
+ réf: [BUG J005]
+ * better handling of non Ivy broadcast messages
+ $ jprobe
+ $ echo coucou | nc -q 0 -u -b 127.255.255.255 2010
+ throws a numberformatexception and stays in a unstable mode for the
+ relevant domain.
+
1.2.2
- java fr.dgac.ivy.Probe
- ivyprobe, quitte ivyprobe
@@ -116,8 +139,7 @@ Not a bug ?
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.
-
+ 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
diff --git a/Changelog b/Changelog
index 7f8776b..44fa5ef 100644
--- a/Changelog
+++ b/Changelog
@@ -1,4 +1,70 @@
--------------------------------------------------------------------
+1.2.6
+
+ documentation
+ - the manual has been heavily updated, and C++ has been left out.
+
+ new features
+ - IvyClient now sends back an error message when an incorrect regexp is sent
+ the message is supposed to be readable
+ - uses apache jakarta-regexp instead of gnu-regexp ( see
+ http://jakarta.apache.org/regexp/ ), we gain a compatibility with Perl
+ and the new ivy-c 3.4.6 :)
+ - no more java ping in Probe ...
+
+ API changes
+ - Ivy changed changed the semantic of -b a,b:port,c:otherport if no port is
+ specified for a, it take the port from the next one. If none is
+ specified, it takes DEFAULT_PORT
+ - no more asynchronous sending of message ( async bind is ok though )
+ because the tests are sooooo unsuccessful
+ - IvyWatcher's getDomain now sends IvyException for malformed broadcast addresses
+
+--------------------------------------------------------------------
+1.2.5
+
+ no more java ping ... It was considered useless
+
+ new features
+ - Ivy protectNewLines to add encoding end decoding of \n within messages
+
+--------------------------------------------------------------------
+1.2.4
+
+ bugfixes
+ - resists when a non Ivy Agent broadcasts on our address
+ - invokes disconnect() on a normal IvyClient end of run()
+ - bus.start(null) now *really* starts on IVYBUS property or 127:2010 if the
+ property is not set
+ - bugfix J007 : breaks connexions with remote clients using a faulty
+ protocol, ignore subscriptions to faulty regexps.
+ - bugfix J006 : invokes the applicationListeners's disconnect method at the
+ end of the run() loop
+ - the IvyWatcher accepts connexions from remote hosts with the same port
+ number. Closes a possible bug, yet to check thoroughfully...
+ - bugfix J005 : the IvyWatcher's loop doesn't break on faulty broadcasts,
+ belonging to non ivy application, e.g.
+ - major rewrite of the internals of the Ivy class structure
+
+ new features
+ - added a sendToSelf(boolean) method in the Ivy class to allow the
+ sendMsg() to trigger our own callbacks. Default is false.
+
+ API Changes (WARNING, you might have to recompile you applications)
+ - changed the API for Ivy.sendMsg and IvyClient.sendDirectMsg, both function
+ can now raise an IvyException if the message contains \n or \0x3
+ - changed the API for IvyApplicationListener ( die now requires a String
+ argument ).
+ - changed the API for Ivy.bindMsg(). It now raises an IvyException if the
+ regexp was not compiled successfully (e.g.: "(.*").
+ - added an IvyBindListener and Ivy.addBindListener, Ivy.removeBindListener
+ order to hook callbacks upon reception of bind requests. It is now
+ possible to write a decent ivy monitor program. JProbe has been rewritten
+ this way and now displays the subscriptions in real time, not only at
+ startup ( should I file a bugreport against ivy-c ? )
+ - Probe can send messages to itself, with the -s command line switch
+
+--------------------------------------------------------------------
1.2.3
new features
diff --git a/Makefile b/Makefile
index 3a199b9..aa49b3d 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,9 @@
# Be sure to set this before compiling ...
- VER = 1.2.3
+ VER = 1.2.6
DIST = lib/ivy-java-$(VER).jar
DOCS = doc/html/api
+ #JAR = fastjar
+ JAR = jar
all: class examples
@@ -10,6 +12,7 @@ examples:
class:
( cd src; make; )
+ grep -H TODO src/*java
docs:
( cd doc; make; )
@@ -18,14 +21,17 @@ docs:
#dist: class docs
dist: class
ln -sf src/fr .
- ln -sf /usr/share/java/repository/gnu .
- fastjar cvfm $(DIST) manifest fr/dgac/ivy/*.class gnu src/Makefile src/*.java examples/*java examples/Makefile doc/html/api/fr/dgac/ivy/*html doc/html/api/*html doc/html/api/*css README COPYING.LIB doc/ivy-java.pdf doc/ivy-java
- rm -f fr gnu
+ ln -sf bundle/gnu .
+ ln -sf bundle/org .
+ $(JAR) cvfm $(DIST) manifest fr/dgac/ivy/*.class gnu org src/Makefile src/*.java examples/*java examples/Makefile doc/html/api/fr/dgac/ivy/*html doc/html/api/*html doc/html/api/*css README COPYING.LIB doc/ivy-java.pdf doc/ivy-java
+ rm -f fr gnu org
jar: class
ln -sf src/fr .
- fastjar cvfm lib/ivy-java.jar manifest fr/dgac/ivy/*.class src/Makefile src/*.java README COPYING.LIB Changelog BUGS gnu examples/*.java
- rm -f fr
+ ln -sf bundle/gnu .
+ ln -sf bundle/org .
+ $(JAR) cvfm lib/ivy-java.jar manifest fr/dgac/ivy/*.class src/Makefile src/*.java README COPYING.LIB Changelog BUGS gnu org examples/*.java
+ rm -f fr gnu org
clean:
( cd src; make clean ;)
diff --git a/README b/README
index d5af1c2..d30cfcd 100644
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
ivy-java README
-Last modificiation, lun jan 6 16:25:35 CET 2003 , Yannick
+Last modification, lun jan 6 16:25:35 CET 2003 , Yannick
-----------------------------------------------------------------------------
Ivy java is open source software distributed under the terms of the GNU
@@ -79,7 +79,10 @@ BUG REPORTS
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
+ http://www.tls.cena.fr/products/ivy/download/desc/ivy-java.html.
+ Don't hesitate to ask me by mail a cvs snapshot if you're not satified with
+ the upstream release.
+
Thanks!