[Seaside] Re: What's the (technical) purpose of adding t/seaside/to the path

Carl Gundel carlg at libertybasic.com
Fri Jul 20 20:35:36 UTC 2007

For this Boris pointed me at the SeasideShortPath parcel that comes with VW. 
My paths went from http://mydomain.com/seaside/go/myapp to 
http://mydomain.com/myapp.  Much better.  However I do agree that it should 
not require a patch.  It should be easy to configure out of the box and easy 
to reconfigure when the need arises.

-Carl Gundel, author of Liberty BASIC

----- Original Message ----- 
From: "Michael Lucas-Smith" <mlucas-smith at cincom.com>
To: "Seaside - general discussion" <seaside at lists.squeakfoundation.org>
Sent: Friday, July 20, 2007 9:05 AM
Subject: Re: [Seaside] Re: What's the (technical) purpose of adding 
t/seaside/to the path

>> But the thing is, they will probably want *something*, and as soon as you 
>> want that you are talking about configuration.  But again, I point back 
>> to the fact that if you are deploying then someone has to know how to 
>> deploy with your chosen web server, whether that be Apache, Webtoolkit, 
>> Commanche, whatever.  And knowing how to rewrite URLs is part of knowing 
>> your deployment.
> That's a fair argument. I still think you'll turn away some pedants by 
> having the URL there in the default image, but it is a nice advert. I'll 
> just note it as something to be document for VisualWorks.
> Michael
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list