[Seaside] KomHttpServer to serve Seaside on port 8888 and stand-alone content on port 80 at same time

[Sean Allen]

Why do you want to serve the static content via kom?

On Mon, Aug 16, 2010 at 10:39 AM, Tim Murray <tmurray at ecsorl.com> wrote:
> I have static html pages that are not developed in Seaside, that I would
> like to reference from within Seaside without having to go the Apache route.
>
>
>
> Currently, I have have an I-Frame in a seaside component that displays this
> stand-alone content just fine. However it is served by an Apache server.
>
> I would like to serve it via the KomHttpServer on my Seaside image.
>
>
>
> Good idea? Bad idea?
>
>
>
>
>
> Thx
>
>
>
> t.
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>