durusmail: quixote-users: Making Quixote work in a threaded Web server.
Making Quixote work in a threaded Web server.
2002-10-04
2002-10-04
2002-10-04
2002-10-04
2002-10-06
2002-10-07
2002-10-16
2002-10-16
2002-10-16
2002-10-16
2002-10-17
2002-10-17
2002-10-17
2002-10-16
2002-10-16
Making Quixote work in a threaded Web server.
Titus Brown
2002-10-16
-> 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.

great, thanks!

-> > 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?

After being called on my boast ;), I realized it's a bit trickier than I'd
originally thought to do it in a non-Web-server-specific way.

Having publisher index itself by root_namespace would be the simplest, I
think; then for each request, decide which publisher should be returned by
get_publisher().

You could even write a wrapper around quixote that set _publisher according
to the URL being used before calling publish().  Ugly, and clearly not
something that Quixote was designed for .

--titus

reply