Quoting Berin Loritsch <[EMAIL PROTECTED]>: > I would like to see about getting the Avalon Event package migrated to > commons, > which really has little to do with Avalon itself. In contrast to the > current > Jakarat Commons Event package, the Avalon Event package is developed with > the > Staged Event Driven Architecture (SEDA) style programming in mind. > > It includes the core classes for setting up a CommandManager which will > accept > commands from many sources and run them in a small pool of threads (powered > by > Doug Lea's excellent thread management utilities). That pool of threads can > be sized relative to the number of processors, and it has other necessary > tools > to create a set of stages with events piped through it. There is also a > managed > pool that uses the CommandManager to manage the size of the pool in the > background. > > Considering that these things are necessary for Avalon projects, but it is > not > the core art there, I believe that this community would be the best location > for it. I want to make sure that this community would be willing to host it > (of course I would help sponser it and maintain it as necessary), but that > it > would stand a better chance of getting a community behind it to make it more > robust. >
Sounds intriguing to me. Of course, if I had infinite free time, it would be fun to think about a commons package that did the whole SEDA-type thing, to give you a generic platform on top of which to build network server apps that use asynhronous I/O in Java. But the event processing model is a good start down this path, and generally useful in other environments to boot. Craig > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
