[Seaside] About Seaside 3.0
Victor
vmgoldberg at verizon.net
Sun Jul 13 02:46:54 UTC 2008
Hola querida,
Esta todo bien?
Te llame hoy durante el dia al cell phone y nunca hubo respuesta.
Te llame a la mañana y no estabas en tu casa. Te acabo de llamar y no hay
nadie ahí.
Por favor decime.
Love,
V.
----- Original Message -----
From: "Ramon Leon" <ramon.leon at allresnet.com>
To: "'Seaside - general discussion'" <seaside at lists.squeakfoundation.org>
Sent: Saturday, July 12, 2008 10:24 PM
Subject: RE: [Seaside] About Seaside 3.0
>> Philippe,
>>
>> Why? That then forces users to set up Apache, and then configure it
>> correctly. Squeak/Pharo should be able to do SSL on its own, and can
>> thanks to the cryptography group's efforts. With some extra
>> effort, it
>> could serve secure pages on its own. Just about any otherwise
>> non-Seaside service could benefit from such a simple to manage secure
>> web server.
>>
>> Bill
>
> Bill, a simple question, why do so many Smalltalker's insist on
> reinventing
> the wheel? Apache isn't just a web server, it's *the* platform of the
> Internet and it's not some trivial thing to simply reimplement and replace
> everything it can do for you out of the box. Isn't it about time to learn
> how to play nice with the outside world and stop insisting that every
> single
> piece of the tool chain be implemented in Smalltalk?
>
> Despite what you're implying, Apache is not that difficult to setup and
> there's tons and tons stuff available for making it do anything you want.
> As for setting it up with Seaside, you could easily find a dozen different
> working configurations prewritten with a trivial look through the Seaside
> forums. Yes, that stuff should be easier to find, possibly posted on the
> seaside.st site in a visible place. With a prewritten config, setting up
> Apache probably takes less time than installing Seaside. This is all it
> takes...
>
> <VirtualHost *:80>
> ServerName yoursite.com
> DocumentRoot /var/www/yoursite.com
> RewriteEngine On
> ProxyRequests Off
> ProxyPreserveHost On
> UseCanonicalName Off
> RewriteRule ^/seaside/files(.*)$ http://localhost:3001/seaside/files$1
> [P,L]
> RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
> RewriteRule ^/(.*)$ http://localhost:3001/seaside/yoursite/$1 [P,L]
> </VirtualHost>
>
> Is it really worth all that effort to avoid this tiny little config file
> and
> avoiding using one of the most solid, stable, and powerful tools available
> to you?
>
> Ramon Leon
> http://onsmalltalk.com
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
More information about the seaside
mailing list