[Seaside] Integrating Images on a website. Don't want to use
Apache or WAFileLibrary.
m.coba.m at gmail.com
Wed Apr 23 21:11:40 UTC 2008
I don't understand the issue with portability in having the static content
served by a web server (apache, lighttpd, nginx).
In fact, it is not even practical to deploy an app (used for more than a
couple users) without a kind of proxy/load balancer in front.
You can let the web server do what does the best, serving static content and
the seaside to to what it does best, to run your app.
Never will Seaside, or comanche or (mongrel in ruby on rails case for the
matter) be on par with a web server in serving static data.
And you don't have to have a lot of user to decide to upgrade from "all in
the image" to using a "just the app in the image/else on webserver" setup.
>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)
On Wed, Apr 23, 2008 at 3:30 PM, Torsten Bergmann <astares at gmx.de> wrote:
> 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" or read
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside