concerning the first problem, I think Steve is right, the best way is to
pass "self" around. You can also make the functions methods of the class
that gets "self" as a parameter when instantiated. But the proper way
would be to use <%@ page extends="MyPage"%>, where MyPage is a subclass
of PSPPage, with additional functionality that you need in the
particular page(s). You can also have multiple base classes or mixins.
I think that's the "Webwarish" way to use PSP.
Another option is using the PSP directive <%@ include ... %> instead of
importing the file.
By the way, the Page class has some convenience methods: Instead of
self.response().write(...) you can simply use self.write(...), or
isntead of self.request().session() you can use self.session(). See:
In the upcoming Webware 1.1 versions, it will also be possible to use
self.response instead of self.response(). But the old notation will
continue to work.
Concerning the second problem, you're right - .html files are always
served as they are, i.e. not parsed by PSP. The extensions that are
parsed for PSP are returned by PSP.PSPServletFactory.extensions(). I'll
make this configurable in the next version; for the time being you can
patch this easily if you like.
Concerning psp-handler, you should probably not use it in this version,
I'm going to fix a problem here that has just been reported.