> Embeding james in databases is not as silly as you seem to think, Dan
> Debruner proposed embeding james in derby a couple of years ago.
> Admins want to run the products they know, and as little else as
> possible.
That's generally down to laziness, not good architecture. And it can hamper
other things.
For example, let's say that you take JAMES and embed it into the web container.
- What happens when you decide to cluster your web container?
- How does it effect your network topology? Firewalls, DMZ, etc?
And what are you using JAMES for in the web container?
There is clearly a value to refactoring our component architecture, and
possibly one in allowing JAMES to move into a J2EE container. But the Web
container isn't the right place for it. The EJB container comes closer.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
