Someone else and Jay attempted to put "embedded servlet URLs" into the
WebKit server, but admittedly, I broke them when I overhauled the
serverSidePathForRequest() code to work simultaneously for various test
cases. The idea was that if you had this URL:
Then books might actually be a servlet, such as books.py, which would then
have access to "war_and_peace/edit" via a request method like extraURLPath().
Or for that matter, war_and_peace could be the servlet.
I would have no objection to putting this back in provided that it:
* could be turned off via configuration (there are performance and
* is accompanied by full test cases
* existing test cases continue to work (see the Testing context off the
Examples or Admin page)
The code is still in there, but has "if 0:" in front of it.
It's still not quite the same as Zope, but it does add additional power and
expressiveness for how to arrange your site.
However, it's not on my personal list, so if someone wants it, someone else
besides me will have to jump in.
At 09:53 AM 11/15/00 -0500, Geoff Talvola wrote:
>One more comment on object publishing, Zope-style:
>One of the claimed advantages of Zope is that you can address your
>objects as part of the URL, which is more elegant and readable. For
>Whereas in other systems like WebKit you may have to do something like:
>However, in my limited experience with Zope, I've found that in practice
>you usually have to auto-generate the ids of the objects, or else make
>your users go through extra work to choose an appropriate ID that can be
>embedded in a URL. So with auto-generated IDs it ends up looking more
>In which case I actually prefer the second syntax. In other words,
>since you frequently have to auto-number things anyhow, the supposed
>advantage in readability/elegance of the Zope method evaporates.
>- Geoff Talvola
> Parlance Corporation
>Webware-discuss mailing list