1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
|
--------------------------------------------------------------------
1.2.6
documentation
- the manual has been heavily updated, and C++ has been left out.
bugfixes
- major cleanup to handle simultaneous connections, e.g., between two
busses within the same process ( AsyncAPI test is very stressful )
I made an assymetric processing to elect the client that should
disconnect based on the socket ports ... might work...
- jakarta regexp are not meant to be threadsafe, so for match() and
compile() must be enclaused in a synchronized block
- now sends back an error message when an incorrect regexp is sent
the message is supposed to be readable
- IvyWatcher now uses a new buffer for each Datagram received, to prevent an old bug
new features
- added serial numbers for traceDebug
- Ivy.waitForMsg(regexp,timeout) and Ivy.waitForClient(name,timeout) make
the synchronization with other Ivy agents easier. Wait "forever" if
timeout is null.
- 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
- 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 )
- handles the different JVMs more cleanly in the makefiles
- testbenches OK for linux jdk from 1.1 to 1.4
bugfixes
- the datagram sender is encapsulated within its own thread. Closes
another bug.
- 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),
- handles the InterruptedIOException happening on certain thread
conditions in jdk1.1 and jdk1.2. Threads and multiple VMs is a very
complex mix.
known bugs
- there is an Interrupt on Blackdown linux leading to an innocuous error
message. I will investigate later ... It is OK on Solaris jvm 1.1.7A.
- in Linux jdk1.2.2, a SIGSEGV from time to time.
------------------------------------------------------------------------------
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
|
