Sorry Brett :)

	the two images is nothing about Magma. You can if that is convenient for
you. I think it will depend more on the load limits (few seaside sessions per
image works better).

	By the way if you can set all in one image why use the tcp/ip at all?
Are you sure you need Magma at all? Do you have ACID kind of requeriments?

	cheers,

Sebastian Sastre


 

> -----Mensaje original-----
> De: squeak-dev-bounces at lists.squeakfoundation.org 
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org] En 
> nombre de Brett Kosinski
> Enviado el: Jueves, 27 de Marzo de 2008 13:53
> Para: The general-purpose Squeak developers list
> Asunto: Re: [squeak-dev] Magma and shared sessions.
> 
> > Hi Bert,
> 
> Brett ;)
> 
> >         I don't think I get what are you trying to do in 
> the way you talk about.
> >
> >         Maybe you just need:
> >
> >         1. A seaside application whith Magma ODB reachability
> >         2. Another image in another host (or even same 
> host) with reachability
> >  to the same ODB
> 
> Yes, that's certainly one option.  But why two images?  Is there a
> reason I can't achieve the same with a single image (I'd prefer to
> have all the software related to this project stored in a single
> image... it makes things much easier for me to manage).  Or is there
> something inherent in Magma that makes this arrangement unreasonable?
> 
> Brett.
>