On 16 October 2002, Titus Brown said:
> Nope.  Multiple requests per publisher will now be *possible* with a
> subclass; they are not currently, and (unless you want to check in the
> threaded subclass code, below) would not be part of the default
> Quixote distribution.

OK, gotcha.  I wasn't clear on why you wanted separate methods for
setting/clearing/getting the request object -- now I am!

BTW, note that I renamed set_request() and clear_request() to
_set_request() and _clear_request() -- the underscore denotes that this
is internal to Publisher, but subclasses are allowed to play with them.

> As to what code I override in a subclass, imagine a subclass of Publisher,
> ThreadedPublisher, with the following functions:

Probably belongs in documentation -- I'm reluctant to include code that
we don't use and isn't widely used by others.  I'll go start
doc/multi-threaded.txt now.

> Incidentally, I'd be happy to make a (trivial!) patch to fix the
> mod_python problem, but it would only benefit people who want to have
> multiple publishers in one process -- not, IMO, a good idea for
> clarity.

It sounds like a mod_python problem to me, not a Quixote problem.  And
if mod_python provides the fix, I'm content to let it lie.

However, I'm curious: what did you have in mind?

        Greg