I'm still unhappy with the 2.2.0 CVS at the moment to be honest..
There still are some very nasty bugs that need to be solved with the integration of amuleweb and the daemon. For example,
* From the docs i read, you can only connect to KAD if you manually click on the Connect button (instead of, say, double clicking on a server or whatever). This cannot be done through amuleweb.. I haven't found a way through amuleweb to do so.
* Clicking on the Connect button from amulegui doesn't work.
* amulecmd also doesn't seem to connect properly.
* amuleweb shows KAD as one state, while amulecmd shows it as another state, while amule shows it as a third state.. which is it? connected? disconnected? firewalled?
* amuleweb is really weird when it comes to connecting to Servers.. It's too fast, doesn't give you a good log, and hardly ever connects, while you can connect in seconds through aMule.
* I still can't search.. Searching through amuleweb gives no results. Searching through amule sometimes gives results. I'm not sure if this is a server thing or not.. but i always search on Global.
* I still get amuleweb segfaults on amd64 using it.
This is what i can remember from the top of my head. I hope it helps.
As soon as i get a new router that supports upnp and forwarding more than 10 ports, i'll get to testing aMule on OS X.
