[Seaside] Possible OT: Strange Seaside/VW oddity -- Is there
some sort of cacheing in Seaside/VW or ??
m.bany at wanadoo.fr
Sat Mar 25 09:43:56 UTC 2006
> read(9, "GET /seaside/go/mywebapp/css/screen.css HTTP/1.0\r\nHost:
> 10.0.1.198:8008\r\nUser-Agent: Mozilla/5.0 (Windows; U; Windows NT
> 5.0; en-US; rv:1.7.12)
URLs that start with "/seaside/go" will always take you to a Seaside page.
URLs that start with "/seaside/go/mywebapp" will always take you to a
page of Seaside application "mywebapp".
With WebToolkit, the first token in the URL, a.k.a. "seaside" is known
as the WebSite name. A WebSite is able to
serve static files, Smalltalk Server pages (i.e. templating) and
servlets. In VW, Seaside runs as a WebToolkit servlet
and when the URL starts with "/seaside/go" the Seaside servlet is used.
The Seaside servlet uses the rest of the URL,
a.k.a. "mywebapp" for dispatching to the right Seaside component.
With WebToolkit, a WebSite has a reference to a directory name on the
hard disk. For instance, assuming a WebSite
named "seaside" is mapped to directory "C:\WebSites\Seaside", a URL like
"/seaside/css/screen.css" will serve file
A WebSite can be defined in two ways.
(1) Smalltalk code, see AAADocumentation >>createWebSite
When you install vanilla SeasideForWebToolkit, this method gets executed
and you get a standard WebSite
named "Seaside", for namespace "Seaside" pointing to
$(VISUALWORKS)\web\examples and with "go"
set for the Seaside servlet.
(2) ini files, see the ini files in the $(VISUALWORKS)\web folder
See the documentation in $(VISUALWORKS)\doc\
More information about the Seaside