> Yes, the project is still active, although the amount of development work
> over the past year has been minimal due to my work commitments. That said,
> I do want to continue the project - and appreciate your offer of help.
> There are a few pending TODOs that need to be done to finalized 0.5 and
> bring it out of 'beta' - including updating to the latest version of Derby,
> and the latest version of the HTTPClient. There is also a bug that I need
> to fix related to URL-based authentication, and a couple of outstanding bugs
> related to categories - have you used these much?

Well no I didn't use them that much, but just once.

>
> Another thing that I really would like to do (and maybe this is also
> something you could help with) is spend some time tuning the Derby database
> and how nntp//rss uses it (indexes etc) - the main goal being to improve
> performance, and also provide a set of tuning parameters that, for machine
> with restricted resources, will reduce the amount of memory it uses.

Ok

>
> Finally, one thing that would be very useful - and is definitely missing -
> is a collection of automated test cases that exercise the whole system. I
> had envisioned an automated test environment using JUnit and Jetty (to act
> as a web server to serve up RSS/ATOM feeds over HTTP/HTTPS) - but never got
> around to starting that development.

For unit testing may I recommend TestNG (http://testng.org/) instead of
JUnit, it's supposed to be more powerful and flexible (I never used it
though).

Well.. where/when do I start ? :)

BoD