Squeak + Seaside questions

> Hi seasiders,
>
> I've been developing on seaside but only as a hobby, i'm really having
> fun programming for the web, which hadn't happened to me for a long
> time now.
>
> Right now i've been asked to work on some project and i feel really
> tempted to develop this in seaside, but i still have some questions
> and could use some help to decide if squeak + seaside is actually an
> option. Some of my doubts are:
>
> 1) I believe squeak + seaside only serves one request at a time, is
> this right? If so, how will an application that is to serve 1-10 users
> simultaneously behave in terms of performance?
>
> 2) Is it possible to have the application seamlessly deployed together
> with Apache 1.3.37? All the documents i've found rely on stuff that
> apparently are only available on Apache 2.x. (If someone could provide
> some tips i'd be thankful)
>
> 3) How is squeak + seaside in terms of scalability, is it possible to
> add multiple applications running on the same VM and have them not
> colliding with each other? (Continuations still make my head dizzy,
> that's why i ask this)
>
>
> I know some of these might be really easy/dumb questions, but these
> come to mind as a newbie on seaside at this moment when i need to
> assure if seaside is really an option for this project. Thanks in
> advance to anyone for the patience and help.
>
>
> Best regards,
>
> Alexandre Paes
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>

>> 1) I believe squeak + seaside only serves one request at a time, is this
>> right?
>
> No, that's not true.
>
>> If so, how will an application that is to serve 1-10 users
>> simultaneously behave in terms of performance?
>
> 10 users should be easily handled by a single image.
>
>> 2) Is it possible to have the application seamlessly deployed together
>> with Apache 1.3.37? All the documents i've found rely on stuff that
>> apparently are only available on Apache 2.x. (If someone could provide
>> some tips i'd be thankful)
>
> It is easier with Apache 2, but it works with any other web server as
> well. What you have to do in this case is to set server-name and port
> in the Seaside configuration, so that Seaside can properly generate
> absolute URLs.
>
>> 3) How is squeak + seaside in terms of scalability, is it possible to
>> add multiple applications running on the same VM and have them not
>> colliding with each other? (Continuations still make my head dizzy,
>> that's why i ask this)
>
> Yes, that's no problem.
>
> Depending on the amount of concurrent users you might want to add more
> VMs and do some load-balancing. This should not be necessary for 10
> users though.
>
> Lukas
>

>
>
> Thanks everyone for the replies and help,
>
> Alex
>
>
> Em 10/08/07 18:23 Lukas Renggli escreveu:
> >> 1) I believe squeak + seaside only serves one request at a time, is this
> >> right?
> >
> > No, that's not true.
> >
> >> If so, how will an application that is to serve 1-10 users
> >> simultaneously behave in terms of performance?
> >
> > 10 users should be easily handled by a single image.
> >
> >> 2) Is it possible to have the application seamlessly deployed together
> >> with Apache 1.3.37? All the documents i've found rely on stuff that
> >> apparently are only available on Apache 2.x. (If someone could provide
> >> some tips i'd be thankful)
> >
> > It is easier with Apache 2, but it works with any other web server as
> > well. What you have to do in this case is to set server-name and port
> > in the Seaside configuration, so that Seaside can properly generate
> > absolute URLs.
> >
> >> 3) How is squeak + seaside in terms of scalability, is it possible to
> >> add multiple applications running on the same VM and have them not
> >> colliding with each other? (Continuations still make my head dizzy,
> >> that's why i ask this)
> >
> > Yes, that's no problem.
> >
> > Depending on the amount of concurrent users you might want to add more
> > VMs and do some load-balancing. This should not be necessary for 10
> > users though.
> >
> > Lukas
> >
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

>> I don't get why seaside insists on generating absolute urls at all.
>> It seems to be bad practice.
>
> HTTP redirects are required to be absolute. Most browser can handle
> relative redirects, but it is syntactically wrong.
>
>> Consider one apache doing load
>> balancing to multiple application servers.  Seems more flexible to
>> use relative urls (and, in fact, this is the first hack I make to any
>> seaside - I kill off the absolute url code).
>
> That's not a issue, because Seaside can automatically detect the
> currently used host-name using Apache 2.
>
> Cheers,
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

>> First - there's no apache when I'm developing.
>> Second - not a lot of hosting providers have approved apache 2 (like
>> mine).
>> Third - moving an image to a new box where the hostname has been set
>> prevents access to the web tools to change the host name.
>
> Having different configurations for the different environments would
> solve all these problems.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> -----Original Message-----
> From: [hidden email] [mailto:seaside-
> [hidden email]] On Behalf Of Todd Blanchard
> Sent: Wednesday, October 10, 2007 1:20 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Seaside and absolute URLs
>
> Yes - that would be good.  Just wanted share the pain I experienced
> trying to move an image to a new machine - even the config app
> wouldn't work.  :-(
>
> Very frustrating it was.
>
> On Oct 10, 2007, at 12:33 PM, Lukas Renggli wrote:
>
> >> First - there's no apache when I'm developing.
> >> Second - not a lot of hosting providers have approved apache 2

> >> prevents access to the web tools to change the host name.
> >
> > Having different configurations for the different environments would
> > solve all these problems.
> >
> > Lukas
> >
> > --
> > Lukas Renggli
> > http://www.lukas-renggli.ch
> > _______________________________________________
> > seaside mailing list
> > [hidden email]
> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside