On 26/12/2007, Giovanni Corriga <giovanni at corriga.net> wrote:
> Igor Stasenko ha scritto:
> > On 26/12/2007, Philippe Marschall <philippe.marschall at gmail.com> wrote:
> >>> For Seasiders, there now a good perspectives to have a single 'main'
> >>> image, which accepts incoming connections, and do load-balancing
> >>> between smaller images which do all dirty work.
> >> How would that work? How would you pass a request to a different
> >> image? How would it return the response? How would you keep the images
> >> in sync (deploy code to all the images)?
> >
> > See, Hydra VM is just VM it's not a smallatlk application (such as
> > Seaside). And of course, to resolve all of the above there a lot to do
> > and think of.
>
> Two possible solutions:
>
> - have a common protocol for Channel and Socket operations, so that Kom
> may listen either on the former or on the latter without changing any code.
>
> - use a Kom variant that knows it's a "slave" process in one of the load
> balanced images. In this case, it could use channels to receive
> HttpRequest objects from and return HttpResponse objects to the load
> balancing image.
>

I think, the latter is more appropriate, because channels don't have
'listen/accept' semantics. Once channel is created, it starts
listening for incoming data, not connections.
But this can be easily changed by introducing a framework on top of
that. For instance, you can create a channel which will listen for
'connections', and then upon request, it creates new channel and
sending it's name/id in response which will be used to receive
incoming data.

>         Giovanni
>
> PS. Great work, Igor (and Andreas, too)!
>
>
>

-- 
Best regards,
Igor Stasenko AKA sig.