preparing release v0.2.0

SVN Revision: 34

CHANGES

@@ -0,0 +1,17 @@
+0.1.1 -> 0.2.0:  Major Feature Enhancements (not yet released) 
+	- add 'realtime' stats
+	- add new 'parse' type of protocol
+	- add reconnection support (persistent client)
+	- add basic HTTP and HTTPS support
+	- split the application in two parts: a single controller (tsunami_controller),
+      and the clients (tsunami)
+	- switch to R9B
+
+0.1.0 -> 0.1.1:  Bugfix realease (Aug 2002)  
+	- fix config file
+	- fix few typos in docs
+	- fix init script
+	- few optimizations in user_server.erl
+	- switch to R8B
+
+0.1.0: Initial release (May 2001)  

README

@@ -64,7 +64,9 @@
   useful measurements of responses time. An small script is furnished
   for the Jabber protocol (mean, median, standard variation, and so on
   are computed, for different types of messages: authentication,
-  chat, offline messages ...)
+  chat, offline messages ...). 
+  Since v0.2.0, stats can also be computed in real-time, and dumped in
+  a text file at regular interval.
 
   This software is currently under development and can be enhanced
   in many ways (see TODO file). 
@@ -73,7 +75,7 @@
 
   2.1.  Dependencies
 
-  - requires Erlang/OTP R7B-0 or up (tested with R7B-2)
+  - tested with Erlang/OTP R9B-0
     (http://www.erlang.org/download.html)
 
   - perl5 (if you want tu use the scripts)
@@ -85,8 +87,8 @@
   Edit Makefile and idx-tsunami.pl if you want to change the install
   path (/usr/local/idx-tsunami by default)
 
-  Edit src/tsunami.rel.src if your Erlang version is not R7B-2 and set
-  erts, kernel and stdlib version according to your Erlang
+  Edit src/tsunami.rel.src if your Erlang version is not R9B-0 and set
+  erts, kernel, ssl  and stdlib version according to your Erlang
   distribution.
 
   make
@@ -102,7 +104,9 @@
 
     3/ When it's finished, you can use analyse_msg.pl to get
        statistical results from the logfiles (require at least 'light'
-       monitoring, see comments in 'idx-tsunamirc' )
+       monitoring, see comments in 'idx-tsunamirc' ). With v0.2.0, you
+       can have 'realtime' stats using with the --stats option (no
+       monitoring needed).
 
   2.3.  Problems/Bugs
 

TODO

@@ -1,21 +1,8 @@
 - groupchat for Jabber
 
-- Maybe use a single gen_server instead of 4 (msg, user, request, timer)
-
-- instead of logging everything, let the client (or the monitor)
-  compute stats ?
-
-- Maybe use a single monitor process for all beams ? this allow us to
-centralise the results, (but it can be a bottleneck if too much
-logging data are sent to it ?)
-
-- implement client parsing server response (needed for some protocols)
-
 - clients may do a checksum to control integrity of responses ?
 
-- implement http protocol:
-	- reuse already existing erlang modules.
-	- handle non persistant connections (http/1.0) within a user session
+- http protocol:
     - how to handle http/1.1 pipelining ?
 
 - other useful protocols: ftp, ldap, sql ... ?