Chuck Esterbrook wrote:
> I think Geoff touched on this earlier, but I don't remember how explicit he
> was or how many people connect it with the recent to change to how the
> WebKit app server imports servlets.
> This applies to Webware CVS only. The gist is this:
> From within a directory, you can import servlet classes that are in the
> parent directory.
This sounds like acquisition in training.
Based on my experience with Zope and acquisition, I would say: There are times when it saves a little effort (thought and planning) in the short run, but from a security perspective, it make the site a nightmare to verify. Zope has a lot of code that deals with making sure that an object has the proper security attributes to be used in a given context. Webware has no such support (and probably will not for a while -- Zope, with several paid full-time developers, is still trying on getting it right after two years of wide public exposure.)
My recommendation is exactly what Chuck recommended to me a few months ago, when I complained about security and acquisition: Unless a file represents a concrete document (SitePage is an abstract document), keep it out of the document tree. Put SitePage.py in a lib/ directory in a MySite/ package, then say:
from MySite.SitePage import SitePage
The grey hair you save will be your own.
Of course, if you just want rapid deployment, and don't have sensitive content/code, this may be just the ticket. YMMV.
(Try http://example.org/webkit/MySite/SitePage.py~ after a "quick fix".)