Well, I have one question right off: what is James' _infrastructure_? I gather that it runs in the Avalon container (?) but because the Avalon project seems to have faded out over apache-way I find it difficult to get a handle on what exactly Avalon provides.
Is James using Phoenix, or Loom, or anything like that? Or is the container now self-hosted, as it were? Robert Burrell Donkin wrote: > On Dec 16, 2007 9:17 PM, Chris Rose <[EMAIL PROTECTED]> wrote: >> Yes, I know; it's a pretty far-reaching question, but I'm interested >> in stepping in to try extending some of the mailstore backend, > > cool > >> and to that end I'd love a high-level overview of just what each of the 20- >> odd modules in James are for; what they do and upon what they depend, >> et al. > > http://wiki.apache.org/james/Development/Modularisation contains the > proposal and outlines dependencies. the 3.0 modularisation is very > much a work in process. (if you follow the list for any length of time > you'll discover that we're still debating the best structure). see > (for example) threads: > > * > http://mail-archives.apache.org/mod_mbox/james-server-dev/200711.mbox/[EMAIL > PROTECTED] > * > http://mail-archives.apache.org/mod_mbox/james-server-dev/200711.mbox/[EMAIL > PROTECTED] > > please take a look and feel free to post more questions > > - robert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Chris Rose Developer Planet Consulting Group (780) 577-8433 [EMAIL PROTECTED]
signature.asc
Description: OpenPGP digital signature
