Chimezie Ogbuji ha scritto:
> Hello. I have a problem with a WSGI-based SPARQL server that I have been
> unable to resolve for some time. I was told this is the best place to ask
> :). I'm building a SPARQL [1] server that is deployed as WSGI/Paste
> server. SPARQL queries are handled by the s
No, cannot really be done. This has been discussed a couple of times
on the mod_wsgi list. One such discussion is at:
http://groups.google.com/group/modwsgi/browse_frm/thread/8ebd9aca9d317ac9
In general the same issues apply to all WSGI implementations.
Graham
2009/4/14 Chimezie Ogbuji :
> He
I agree with Ionel
I personally wouldn't rely on "kill wsgi request".
I'd run the update in a subprocess and kill the subprocess
using a signal when the user requests (on unix, of course).
I'd also check a log written by the subprocess to see
whether it completed or not.
If you "kill the wsgi re
That implies one would have extremely reliable tcp connections, and clients
graciously shutdown the connection and the server is notified of that.
Most of the time that doesn't happen and the solution is to continuously
send
keepalive packets (some small string or whatever) - I'm assuming you run
On Mon, Apr 13, 2009 at 10:40 AM, Chimezie Ogbuji wrote:
> Hello. I have a problem with a WSGI-based SPARQL server that I have been
> unable to resolve for some time. I was told this is the best place to ask
> :). I'm building a SPARQL [1] server that is deployed as WSGI/Paste
> server. SPARQ
Hello. I have a problem with a WSGI-based SPARQL server that I have been
unable to resolve for some time. I was told this is the best place to ask
:). I'm building a SPARQL [1] server that is deployed as WSGI/Paste
server. SPARQL queries are handled by the server and evaluated against a
MySQL
