About Seaside 3.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

About Seaside 3.0

Schwab,Wilhelm K
Ramon,

Responding in particular to "it's not some trivial thing to simply
reimplement and replace everything it can do for you out of the box" -
who said I wanted to do THAT?  If one wants the power of Apache, by all
means use Apache.  But for something that acts only as a front end to
configure and monitor something something else, it might make a lot of
sense to build something that can do it w/o installing and maintaining
something as powerful as Apache.

Bill





Ramon Leon ramon.leon at allresnet.com
Sun Jul 13 02:24:30 UTC 2008
===============
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


Wilhelm K. Schwab, Ph.D.
University of Florida
Department of Anesthesiology
PO Box 100254
Gainesville, FL 32610-0254

Email: [hidden email]
Tel: (352) 846-1285
FAX: (352) 392-7029

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

RE: About Seaside 3.0

Ramon Leon-5
> Ramon,
>
> Responding in particular to "it's not some trivial thing to simply
> reimplement and replace everything it can do for you out of the box" -
> who said I wanted to do THAT?  If one wants the power of
> Apache, by all
> means use Apache.  But for something that acts only as a front end to
> configure and monitor something something else, it might make a lot of
> sense to build something that can do it w/o installing and maintaining
> something as powerful as Apache.
>
> Bill

I guess I can understand that desire, I just don't agree because it's based
on the assumption that "installing and maintaining something as powerful as
Apache" is some huge task to be avoided, but it's trivial and not worth any
effort to avoid.  Doing complex things with apache can be a bear, but doing
simple thing is simple.  I know what you want to do, I just feel your
resistance to Apache is more rooted in not wanting to leave Smalltalk or use
a tool that isn't already in your toolbox.

Ramon Leon
http://onsmalltalk.com

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside