Hey folks,
I started working on a prototype yesterday of a server I am developing.
I successfully got the "login" component working, and am thinking about how the login server will forward on successful logons to the "main" server, which controls the main business logic.
I suspect that I will need to put the login application on a different machine from the "main" server, for scalability.
How would you go about doing this with merlin? (i.e. has anyone created a distributed merlin system with different components on different servers ?)
Yep. All of the distributed systems I've built using Merlin have leverages CORBA/IIOP as the underling distribution model. Basically the approach is similar to what Niclas suggested except that in the CORBA environment you have rather rich support for remote activation of components and passing of value objects.
My experience is that the container does not play a terribly important role so long as the overall application remains relatively simple - however, as you get into thing like plugin-processes at the application level you quickly find yourself in a situation where you need greater collaboration between component and container - which is where you will get to appreciate the separation between the component, component model, and the container runtime that exists in Merlin.
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
