Neil said:
> > It's the fact that you are not sure about what they do.

That sounds reasonable to me :)  I can investigate the api more fully.  I have
a hunch I'll conclude the perpestive broker stuff can just get ripped out,
since Qx doesn't use that API, and the synchronization can be left as is in
case a Twisted user is running a multi-threaded server.  Of course, they
could still have other problems in this case, since I'm sure Qx has not been
shaken about in a multithreaded environment very much.


Andrew K. said:
> Jason or someone could ask on the twisted mailing list for a review of the
> code's use of the Twisted APIs.

I can do this.  They're fairly active over there, and Andrew B. has already
provided some troubleshooting guidance in figuring out why the performance
problem existed to begin with.

I'll get this to twisted-web sometime later today.

Jason