Is werx dead?

I`m currently working on a lightweight message solution for in a single vm. Although the website hasn’t been updated for some time ( http://channels.sourceforge.net ) I`m currently working on it at home and in the very near future I want to update the whole website and make some serious work from it.

The company I work for (http://www.jteam.nl ) wants that all employees get involved with opensource projects: assisting projects or creating it themselfes. So this is a good chance to do some serious work on the channels project.

I`m also working on a concurrency library that extends and complements the concurrency library of Java 5. The channels library depends on the concurrency library in some cases.

A great, I’ll take a look, thanks.

I haven’t released any sources. So you can’t download anything.

But in the near future I can give a ‘alpha’ version to you if you want. What are you going to use it for?

I like message buses for intra-application communication. That greatly decouples services from each other.

What did you think of the threading control in Werx? Personally I thought it sucked because you don’t have much control (if I remeber most channels were active by default). The whole idea behind my Channels project is that components should be very configurable and give complete control on the threading behaviour (like blocking, number of threads, priority of threads, maximum number of messages in the buffers etc etc etc)

Yes, the threading in werx is only basic. The nice things in werx, for which I chose it, are:

- easy to develop (Reflection finds channel() methods, no framework dependencies for receivers)
- type safe, type hierarchy
- listen to supertype messages (e.g. all StorageMessages = UserStorageMessage, PageStorageMessage)
- easy to use

Threading wasn’t such a big problem, but more control would be nice.