2. workers2.properties -> workers2.xml using apr_utils xml support. Get rid of 'assumed' properties like figuring out the context from url. Get rid of copying mappings from 'default' to virtual hosts. Of course, it would require few extra 'boring' statements in the config for each mapping.
One of the biggest problems I have /using/ Jk2 is working out what assumptions are going on. I tend to end up making everything explicit in w2.p anyway just so I know what's going on. A well defined XML config syntax would be most welcome.
4. Get rid of all platform specific configuration stuff like WIN32 registry,
event log, apache log, and use only JK2 log.
One thing to consider is a portable method for actually finding workers2.xml in the first place. Windows based connectors tend to put it in the same directory as the dll but that doesn't work as well for unix like platforms which may not easily / sensibly be able to work out which directory the .so is in.
Waiting for response from someone that can 'provide' something different, or just file a veto :) MT.
It sounds reasonable to me and I'm happy to make necessary changes to the Domino connector.
-- Andy Armstrong
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
