diff options
| author | jestin | 2002-06-05 16:21:09 +0000 |
|---|---|---|
| committer | jestin | 2002-06-05 16:21:09 +0000 |
| commit | fe18fefabce1c95f918ac3ef2fcbe0889074990b (patch) | |
| tree | 421195679a6e94f9204c08e37a5b371f3319ea37 /BUGS | |
| parent | 616543fda99482a6e59d0be64553e33819be5559 (diff) | |
| download | ivy-java-fe18fefabce1c95f918ac3ef2fcbe0889074990b.zip ivy-java-fe18fefabce1c95f918ac3ef2fcbe0889074990b.tar.gz ivy-java-fe18fefabce1c95f918ac3ef2fcbe0889074990b.tar.bz2 ivy-java-fe18fefabce1c95f918ac3ef2fcbe0889074990b.tar.xz | |
Mention of the bugs.
Diffstat (limited to 'BUGS')
| -rw-r--r-- | BUGS | 16 |
1 files changed, 15 insertions, 1 deletions
@@ -1,4 +1,18 @@ Known bugs: - it seems not to work with jdk1.1.7A VM. + * it seems not to work with jdk1.1.7A VM. +Fixed: + + * 1.0.11: received an exception: IvyClient.sendBuffer.write failed: Relais brisé (pipe) + It happens while sending messages once a remote client has disconnected + ( fixed in 1.0.12 ) + +Not a bug + + if you send a msg just after the start, it is possible that the message + won't be sent. this is *not* a bug, but, hmmm, a feature. In fact, when you + do start(), it triggers different threads, the broadcasts are sent, and it + is possible that nobody has answered this broadcast by the time you start + sending messages. Try adding an IvyApplicationListener with a callback on + connect(IvyClient) to trigger the launching of messages |