search

jpmccu / sadi

Automatically exported from code.google.com/p/sadi
0 stars 0 forks source link

sadi.py HTTP 502s when service takes too long to execute #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When calling a sadi.py service that takes too long to execute, the client 
receives HTTP 502. Details at https://github.com/timrdf/DataFAQs/issues/4

1) Where is the best practice for "too long" services written on the web (it's 
in the training materials, but I'd like to review the latest version).

2) Could Apache increase its patience?

3) Could sadi.py trickle some results while it's in the process() loop?

Thanks,
Tim Lebo

Original issue reported on code.google.com by tim...@gmail.com on 22 Dec 2011 at 8:02

GoogleCodeExporter commented 9 years ago 
This is not a fault in the client API.  Rather, this is why we have 
asynchronous services (see 
http://code.google.com/p/sadi/wiki/AsynchronousServices).  I'm not sure if the 
Python API implements asynchronous services yet.  If it doesn't, feel free to 
open an issue for that (ideally tagged as Product-PythonAPI and not 
Product-JavaAPI like this one…)

I think it's probably better to ask these exploratory questions on the SADI 
mailing list (http://groups.google.com/group/sadi-discuss) than to open an 
issue for each one.  That way the answers are available for people who search 
for them later.

Original comment by elmccar...@gmail.com on 22 Dec 2011 at 8:10