From: Dan Green <daniel.green@nc...> - 2000-10-05 06:45:30
It's sorta done. I was getting these in my apache log:
Traceback (innermost last):
File "/var/www/htdocs/Webware/WebKit/FastCGIAppServer.py", line 55, in ?
File "/var/www/htdocs/Webware/WebKit/FastCGIAppServer.py", line 20, in mainloop
req = fcgi.Accept()
File "/var/www/htdocs/Webware/WebKit/fcgi.py", line 244, in __init__
socket.error: (35, 'Resource temporarily unavailable')
But it seems to keep working anyway. If anybody out there is an apache/fastCGI
guru and can tell me where the problem is, that'd be great. I think the
problem may be related to the fact that WebKit tends to use the print statement
rather liberally, which may be confusing fastCGI.
I could also be dead wrong.
In any case, the only thing you need to do to install it in your WebKit
directory and make sure fastcgi is the handler for it.
This worked for me:
Alias /WebKit /var/www/htdocs/Webware/WebKit/FastCGIAppServer.py
then, accessing http://localhost/WebKit took my to the default Context.
Let me know if any of this stuff works for you, and more importantly, if
anybody even has any interest in this. (I suppose I should do benchmarks on
this method versus the old FCGIAdaptor->ThreadedAppServer method).
Note that this is single threaded. I'm planning on merging most of the stuff
from ThreadedAppServer into it ASAP.