I was wrong. My filter still doesn't seem to fix the problem
entirely. There is obviously a bug somewhere... either in my code or
in SQLObject.
I will make sure to post an update if and when I figure this out!
Have you had any luck with this? I'm targeting tickets for 0.9, and
this one appears to be hanging.
I played with this for a few hours, and was never able to get any
combination of filters, disabling caching, or clearing the cache to
fix the problem. In my opinion, SQLObject is unfriendly to forking
and multi-process environments at this point, and I simply ran out of
time before I had to deploy the application.
For my application, I ended up using an asyncore-based WSGI/SCGI
server to deploy with, thus working around the problem by keeping
everything in a single process. I am hoping that the bug will be
fixed at some stage so that I can run two or three more of these WSGI
servers and load balance my app behind lighttpd.
I think someone with a bit more SQLObject knowledge should probably
take a look at this problem, and see if they can get it fixed. Not
being able to run in any multi-process environment seems to be a big
issue, at least to me.
-- Jon
