how about a event table in the database? that is definitly a shared
resource. different instances could keep a watch on the table (one thread),
and process all events.
You could implement it like you described but I personaly think using JMS is more appropriated.
If you use a database table you will have to poll (request every x seconds) the database. You have to do this for every MMBase instance. You also have to maintain the table, i.e. you will have to remove changes that are not of any value anymore. A large poll interval will cause server running more out of sync.
Just some thoughts about implementing it in the database.
Rob
