[Seaside] Integrating Images on a website. Don't want to use Apache or WAFileLibrary.

[Janko Mivšek]

Philippe Marschall wrote:

>>  Swazoo is actually able to come very close to Apache, able to serving
>> static content with 300Mbits/s on VW, that is 3 times saturation of 100M
>> Ethernet. This is enough throughput for all except really large websites out
>> there. And of course, you can always switch to Apache or something similar
>> later!

> But even in this case Swazoo will eat CPU cycles from Seaside because
> VW (like Squeak) is single threaded.

Yes, but minimally comparing to Seaside and also not on the same time. 
The web page is namely generated and responded by Seaside first, then 
images start to be served. So, if you serve only one user, this is not 
an issue. Even if you serve many users from the same image, you still 
eat much more CPU by dynamic page generation with Seaside that static 
serving by Swazoo. That's at least my judgment from experiences with 
Swazoo and Aida/Web on VW, which should be similar to Seaside case in 
that respect.

JAnko

> 
> Cheers
> Philippe
> 
>>  Start therefore with Swazoo as pure Smalltalk web server with all pros of
>> being in Smalltalk only, and when needed, switch to Apache. Any you'll see,
>> you won't need that switch soon!
>>
>>  Swazoo vs. Apache benchmark:
>>  http://www.swazoo.org/benchmarks/swazoo-vs-apache.html
>>
>>  JAnko
>>
>>
>>
>>>  From the very beginning you can use all the cpu cicles used for Seaside
>> for your app and not for serving images (that you can't cache in the image
>> as you can in a webserver for faster response, ideally, without disk access,
>> all served from memory)
>>> Miguel Cobá
>>>
>>>
>>> On Wed, Apr 23, 2008 at 3:30 PM, Torsten Bergmann <astares at gmx.de
>> <mailto:astares at gmx.de>> wrote:
>>>    Hi,
>>>
>>>    in general there are three ways:
>>>
>>>     1. serve files using an external server/location (Apache)
>>>     2. create a WAFileLibrary
>>>     3. let the Squeak webserver serve files from hard disk
>>>
>>>    1. is not good for portability, 2. bloats the image - so 3. may be your
>>>    option to choose.
>>>    You can do this either with an WAExternalFileLibrary implementation
>>>    as Holger already explained or by serving the files directly using a
>>>    file serving module for KomHttpServer:
>>>
>>>    For an example either have a look at "Webserver-tbn.4.mcz" in
>>>    "www.squeaksource.com/DeveloperWorkspace
>>>    <http://www.squeaksource.com/DeveloperWorkspace>" or read
>>>
>>>
>> http://www.shaffer-consulting.com/david/Seaside/GettingSoftware/index.html
>>>    Bye
>>>    Torsten
>>>    --
>>>    Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
>>>    Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
>>>    _______________________________________________
>>>    seaside mailing list
>>>    seaside at lists.squeakfoundation.org
>>>    <mailto:seaside at lists.squeakfoundation.org>
>>>
>>>    http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>>  --
>>  Janko Mivšek
>>  AIDA/Web
>>  Smalltalk Web Application Server
>>  http://www.aidaweb.si
>>
>>
>>  _______________________________________________
>>  seaside mailing list
>>  seaside at lists.squeakfoundation.org
>>  http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

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