Lars Kühne - 2004-07-31

Logged In: YES
user_id=401384

Sorry, that is a misinterpretation: Sadly I do not *have* a
re-write, I just said that event persistence would require a
re-write, because the current architecture doesn't allow to
persist events easily (non-uniform handling of different
event types, hashcode used as internal ID, etc.).

A re-write would also tackle some other issues as well:
- Use a thread pool instead of the current
MaxResources/MaxPerformance scheme, so there is only one
execution path to make things more maintainable and testable.
- support different persistence engines, e.g. allow to pass
in an existing Apache OJB PersistenceBroker (or Hibernate or
TopLink or whatever)

I would be interested to try a re-write if I find co-workers
- this is too much work to complete as a one-man show, and
I'm not sure how much time I really can invest. If anyone is
interested, please let me know.

We are in BETA mode for 1.4, and a re-write will definetely
not make it into 1.4.