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)
Miguel Cobá
_______________________________________________
seaside mailing list
seaside@...
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
