I think you should mantain all your assets outside the smalltalk image.
Seaside it is very good with web apps, but it isn't very good at serving
static content. The right tool for the right task. I use lighttpd on debian
to serve all the images (*.jpg, *.gif), css (*.css), javascripts (*.js) for
my app. It has a very small memory footprint, you can use it as a reverse
proxy/load balancer to scale up your app (with several images running as
workers behind lighttpd, and user mod_proxy to serve the static content by
itself and only delegating to seaside what it is your web app.
My advice is: do not try to have all the things inside the image. It is
going to revert back when you try to scale it (think of updating an jpg in
your production app with a lot of smalltalk images working in parallel. A
lot of pain)
Miguel Cobá
On Wed, Apr 23, 2008 at 7:46 AM, aditya siram <aditya.siram at gmail.com>
wrote:
> I am trying to incorporate images into my website.
>> However I would rather not use the methods listed in the "Resources"
> section of the Seaside Tutorial at
>http://www.swa.hpi.uni-potsdam.de/seaside/tutorial. The CSS method reloads
> the image everytime, and the WAFileLibrary method inflates the Seaside
> image terribly. Using Apache as a proxy is not desirable because I am using
> Seaside mainly for its portability ie. I can stick the entire Seaside image
> on a flash drive and move the web-server from PC to PC with minimal hassle
> compared to other frameworks.
>> Is there some way to have the Seaside read the images off some directory
> on the file system?
>> Deech
>>>> _______________________________________________
> seaside mailing list
>seaside at lists.squeakfoundation.org>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>>-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20080423/5ae40f52/attachment-0001.htm