Blast, I never thought about a racked situation. Thanks. Regarding the config.xml, would people be OK with a two parter: -Server side Java wrapper around config.xml. An API would be exposed so other programs, not just mine, could manipulate config.xml. -A Java Servlet based interface that connects to the wrapper and manipulates config.xml
Another question: Are people happier with JSP or Java Servlets? Yes, in the end, they compile out to the same thing, but sometimes I hear quasi-religious wars on which deployment solution is the best ;-) - Anne S On 6/2/05, Hes Siemelink <[EMAIL PROTECTED]> wrote: > Great idea! > > I hope one of the James developers will sponsor this project. > > One suggestion: consider using servlets also for the config.xml > interface. This will make it easier to use when James is installed on a > linux-box somewhere in a server rack. I also think tha developing UIs in > HTML is a lot faster and more flexible than using Swing, as long as your > application is text-oriented. > > Good luck with your project! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
