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

Bany, Michel mbany at cincom.com
Fri Jul 20 10:15:53 UTC 2007

> So I'm wondering for a long time if there a (technical) 
> reason for adding such a path (and seaside/go/ in vw) ?... 
> just out of curiosity... 

This is (was) for a technical reason.

When Seaside is integrated to VW via WebToolkit, we have to
play by WebToolkit rules.

In http://host:port/seaside/go/app, "seaside" represents
the "seaside" site, "go" is a "logical" that represents
the SeasideServlet and "app" represents the Seaside
application. With this construct, it is possible to serve
static files with urls like 
http://host:port/seaside/folder/file.name where the static
files belongs to the same site as the Seaside application.

If you load the SeasideShortPath parcel on top of
SeasideForWebToolkit, then urls like http://host:port/app 
are transparently processedas http://host:port/seaside/go/app, 
unless "app" happens to be the name of a WebToolkit site.

In Seaside 2.7, following a suggestion that was made on
vwnc by Mark Roberts, there is a new option where you can
hook Seaside to the default WebToolkit site rather than
its dedicated named "seaside" site.
See the vwnc thread 

You can select this option in the dialog that pops up while
loading Seaside. If you do so, then in
http://host:port/seaside/app, "seaside" represents the
SeasideServlet and "app" represents the Seaside application.
As a result VW urls are similar to Squeak urls. With this
setup, you can still use the SeasideShortPath parcel to
reduce the urls further.


More information about the Seaside mailing list