[Seaside] HTTP Server Structure

[Sven Van Caekenberghe]

On 17 Nov 2003, at 17:40, Nevin Pratt wrote:
>
> Sven Van Caekenberghe wrote:
>>
>> For example, what is the right/simple way to serve some static files 
>> ? There seem to be several ways of doing it, but I can't get any of 
>> them to work reliably. Where can I learn more about this ?
>>
>
> Here is what I do:
>
> I have a custom subclass of WAKom (which I happen to call 
> ComancheInterface) for connecting Comanche to Seaside. (I use Comanche 
> 5.x, and Seaside 2.x -- Sorry, I've forgotten what the 'x' value is 
> for both of them).

...

> In fact, in hindsight, I doubt I would have bothered with all of the 
> above.  I'd have probably just let my site serve Seaside, and let my 
> Earthlink site serve all of the static stuff.  The static stuff (i.e., 
> pictures) are the most bandwidth intensive-- let it chew up 
> Earthlink's bandwidth rather than mine. :-)  Of course, I pay an extra 
> $19.95 a month for that privilege, but it's worth it.

Google found a previous posting of you where you explained your 
approach - minus the last paragraph. Why did you do it that way ? To 
get both seaside and static http on the same port ? For speed reasons ?

Sven