[Seaside] Swazoo web server (was updateRoot: Weirdness)

Janko Mivšek janko.mivsek at eranova.si
Fri Jul 20 10:50:24 UTC 2007


Janko Mivšek wrote:
> Maarten Mostert wrote:
>> The first thing would just be that it would load without errors in a 
>> clean image.
>> If there is a specific seaside version to select distributed or 
>> published just indicate so on the parcel.
> 
> I just loaded it in VW7.5 (by loading parcel SeasideForSwazoo in 
> Contributed/Seaside) and it loads without a problem, but it don't start 
> on a provided address http://localhost:8080/seaside/go/browse.

Ops, default url is on port 8008:  		

	http://localhost:8008/seaside/go/browse.

> After inspecting SwazooServer singleton, a site (aSeasideSite) and its 
> uriPattern where aSiteIdentifier resists, I found it incorrectly set. 
> This site identifier is somehow set by name of my local machine and 
> external IP, but both should be 'localhost'. Or even better:
> 
>     host:'locahost', ip:'127.0.0.1' port:8008
> 
> If you change that site identifier manually and restart SwazooServer 
> (SwazooServer stop; start), it will work correctly.
> 
> Best regards
> Janko
> 
> PS: Michel, would you correct that until next VW release?
> 
> 
>>
>> I know nothing about webservers so I cannot give you a lot of 
>> feedback. I just try to make some easy to develop and to deploy 
>> website using the smalltalk. I'll try to get some further with the 
>> documentation as indicated.
>>
>> @+Maarten,
>>
>>
>> Janko Mivšek a écrit :
>>> Hi Marteen,
>>>
>>> Maarten MOSTERT wrote:
>>>
>>>> I happened to load the Seaside Swazoo parcels this moring but 
>>>> hm....not so easy to start off. (some more parcel comment maybe)
>>>
>>> For Swazoo 1.0 there is a one page tutorial on a website, while for 
>>> forthcoming Swazoo 2.0 (currently in beta) there is already a bit 
>>> more comments on most important classes.
>>>
>>> And here you can help me a bit: what was your questions when you 
>>> loaded that parcel in the morning? What was your intentions on the 
>>> start? What did you want to achieve? Just look at it or maybe serve 
>>> some static web pages, make another virtual web site?
>>>
>>> By answering you will direct me to prepare a bit more docs on a web 
>>> site...
>>>
>>>> If Swazoo Seaside is the preferred configuration would it not be 
>>>> more cool that VW Seaside loads with Swazoo from the start and adds 
>>>> some Tool extension to get configured ? If I can rent like any 
>>>> dedicated server, upload a VW image and start business that would be 
>>>> really Cool . (Oké James I agree I' have to get a Licence in the 
>>>> mean time).
>>>
>>> Don't forget that Swazoo supports virtual websites, which enables web 
>>> hosting very easily...
>>>
>>> Best regards
>>> Janko
>>>
>>>> Notice that now having some real Seaside tests in VW is really 
>>>> boosting understanding how things work excellent !
>>>>
>>>> @+Maarten,
>>>>
>>>>
>>>>      > Message du 19/07/07 11:16
>>>>      > De : "Janko Mivšek"
>>>>      > A : "Seaside - general discussion"
>>>>      > Copie à :
>>>>      > Objet : [Seaside] Swazoo web server (was updateRoot: Weirdness)
>>>>      >
>>>>      > Dear Seasiders,
>>>>      >
>>>>      > Let me remind you that there is a web server in Smalltalk named
>>>>     Swazoo
>>>>      > (http://www.swazoo.org) and that it was recently ported to 
>>>> Squeak
>>>>     too.
>>>>      > All you need is to connect it to a Seaside. This can be done 
>>>> easily
>>>>      > because it is already done by Michel Bany on VW Seaside.
>>>>      >
>>>>      > That way you get a nicely packed web app server, with easy, out
>>>>     of the
>>>>      > box installation. And from experience so far I can say that
>>>>     Swazoo is
>>>>      > capable to serve small to medium sized public web sites and all
>>>>      > intranets. So, only for really big websites you need to start
>>>>     thinking
>>>>      > to go Apache or lighthttp way ...
>>>>      >
>>>>      > Best regards
>>>>      > Janko
>>>>      > Maintainer of Swazoo
>>>>      >
>>>>      >
>>>>      > sig wrote:
>>>>      > > On 19/07/07, Philippe Marschall wrote:
>>>>      > >> 2007/7/19, sig :
>>>>      > >> > As people says: don't put all of eggs in one basket.
>>>>      > >> >
>>>>      > >> > Serving all content from single image is nice, but its not
>>>>     always
>>>>      > >> achievable.
>>>>      > >> >
>>>>      > >> > As web server, Seaside must serve as front-end for
>>>>     delivering content
>>>>      > >> > on the web, but not dictate, the original source of 
>>>> content.
>>>>      > >>
>>>>      > >> Seaside is not a webserver and not a database layer. It is 
>>>> a web
>>>>      > >> application development framework. Webservers live Apache for
>>>>     lighttpd
>>>>      > >> are preferable for serving static files because this is the
>>>>     job they
>>>>      > >> are really good at and optimized for. They are written in C
>>>>     they use
>>>>      > >> epoll/sendfile and multiple processors and caching and what
>>>>     not. It is
>>>>      > >> a simple one time investment that takes off load of your
>>>>      > >> Squeak/Seaside image and gives it more time and resources to
>>>>     do what
>>>>      > >> it is good and optimized for: dynamic content. That doesn't
>>>>     mean there
>>>>      > >> is no place for a simple solution for simple problems. But at
>>>>     the end
>>>>      > >> of the day for any serious application you will need a 
>>>> standalone
>>>>      > >> webserver.
>>>>      > >>
>>>>      > >
>>>>      > > Hey, lets look to the roots: Seaside serving http requests. 
>>>> And
>>>>     i can
>>>>      > > assure you, that for 99% of the users in the world, thing 
>>>> which
>>>>      > > serving http requests called web-server.
>>>>      > > You may call it web application development framework or
>>>>     anything you
>>>>      > > want, but this will not makes any difference unless you stop
>>>>     handling
>>>>      > > http requests.
>>>>      > > Its a layer, which delivers content to browsers using standard
>>>>      > > protocol and from this point of view, it must be flexible
>>>>     enough to be
>>>>      > > able to deliver any content which developer wants to.
>>>>      > >
>>>>      > > And you saying 'standalone web server'.. It looks like you
>>>>     insist that
>>>>      > > seaside in 90% cases in not complete solution for _BASIC_ web
>>>>      > > solutions?
>>>>      > > Why it must force developer to use third party tools to be
>>>>     complete?
>>>>      > > Its better to be slow, as hog but be COMPLETE rather than 
>>>> flexible,
>>>>      > > complex, but incomplete...
>>>>      > >
>>>>      > >
>>>>      > >> Philippe
>>>>      > >>
>>>>      > >> > Is there something wrong with this concept?
>>>
>>
>>
>>
> 

-- 
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si


More information about the Seaside mailing list