WIP

diff --git a/lib/HACKING b/lib/HACKING
index 884ce2c..38826d4 100644 (file)
--- a/lib/HACKING
+++ b/lib/HACKING
@@ -1,18 +1,22 @@
 HACKING file for libradsec (in Emacs -*- org -*- mode).
 * Design of the libraray
+- three usage models
+  - using send and receive calls in blocking mode
+  - running the libevent loop, getting callbacks
+  - running own event loop, using fd's for select and doing the i/o
+    using libradsec send/receive
 * Functionality
 ** Not implemented
-- reading config file
-- resending packets
+- autoconf/automake/libtool
+- client: matching responses, resending packets
 - custom allocation scheme used in all places
 - callbacks invoked properly
 - server fail over
-- matching responses
 - TLS
 - TLS PSK
-- autoconf/automake/libtool
 - DTLS
 ** Not tested
+- reading config file
 - short read
 - short write
 ** Tested and verified

diff --git a/lib/README b/lib/README
index e221bf1..1a47134 100644 (file)
--- a/lib/README
+++ b/lib/README
@@ -4,8 +4,8 @@ It depends on libradius from FreeRADIUS freeradius-server and
 libevent2.
 
 Those parts of the library which has been tested has been so on Linux
-(Ubuntu 10.04) with libfreeradius2 (2.1.8+dfsg-1ubuntu1) and
-libevent-2.0.7-rc-dev (http://monkey.org/~provos/).
+(Ubuntu 10.04) with libfreeradius2 (2.1.8+dfsg-1ubuntu1), libconfuse0
+(2.6-2) and libevent-2.0.7-rc-dev (http://monkey.org/~provos/).
 
 The file HACKING contains more detailed info on the state of the
 various parts of the library.