[Seaside] updateRoot: Weirdness
philippe.marschall at gmail.com
Thu Jul 19 07:28:24 UTC 2007
2007/7/19, sig <siguctua at gmail.com>:
> 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
> Is there something wrong with this concept?
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside