> I've been skimming through the listserv processors code (AvalonListserv,
> JDBCListserv, & CommandListservProcessor)
Completely different beasts. AvalonListserv & Co are the old list server.
CommandListserv represents a new list server. JDBCListserv is a somewhat
misleading orphan, as far as I've ever figured out. You don't need it to
store lists in JDBC.
> 1. CommandListservProcessor seems to be new to 2.2. Why doesn't it
> extend from GenericListserv?
Because it is fundamentally different code, and intended to replace the old
code, although we want to preserve the old code for people relying upon it.
> 2. Seems like GenericListservManager->AvalonListservManager does not
> use the CommandListservManager structure.
Because they are not related.
> 3. If I use JDBCListserv as my processor, since there is no
> corresponding JDBCListservManager, can I use either
> AvalonListservManager or CommandListservManager?
Don't use JDBCListserv unless you've some special reason having studied the
code.
> 4. Will the GenericListserv code be deprecated in the future in favor
> of the CommandListserv paradigm?
See above.
There is also a James based list server from Japan that has been offered, it
seems to the project. I don't know if Mark has looked at it. One problem
is that the docs are all in Japanese, and no one seems to know how it
compares, or what it offers.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
