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

[aditya siram]

Thank you all for your help!
I have decided to launch an HttpService on another port that allows access
to the directory with all my image files. I have the second server running
but I haven't tested it yet. Since the 'Seaside Tutorial' outlines much the
same concept using Apache I am optimistic that it will work.

Deech

On Wed, Apr 23, 2008 at 11:41 AM, Boris Popov <boris at deepcovelabs.com>
wrote:

> I like having all resources version-controlled together with the code that
> uses them. You can then lazily cache them on the front-end server to avoid
> hitting the Seaside service if you wish, just make sure the URLs have
> version identifier in them if you intend of running multiple versions of the
> application at the same time on the same domain.
>
> -Boris
>
> --
> +1.604.689.0322
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> http://tinyurl.com/r7uw4
>
> boris at deepcovelabs.com
>
> CONFIDENTIALITY NOTICE
>
> This email is intended only for the persons named in the message
> header. Unless otherwise indicated, it contains information that is
> private and confidential. If you have received it in error, please
> notify the sender and delete the entire message including any
> attachments.
>
> Thank you.
>
> > -----Original Message-----
> > From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> > bounces at lists.squeakfoundation.org] On Behalf Of Miguel Cobá
> > Sent: Wednesday, April 23, 2008 9:37 AM
> > To: Seaside - general discussion
> > Subject: Re: [Seaside] Integrating Images on a website. Don't want to
> > useApache or WAFileLibrary.
> >
> > 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
> >
> >
> >
>
> _______________________________________________
> 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/4032a39f/attachment.htm