Issue 13 in sadi: sadi.py HTTP 502s when service takes too long to execute

[sa...@googlecode.com]

Status: New
Owner: elmccar...@gmail.com
Labels: Type-Defect Product-JavaAPI

New issue 13 by tim...@gmail.com: sadi.py HTTP 502s when service takes too
long to execute
http://code.google.com/p/sadi/issues/detail?id=13

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

[Mark]

Surely that would mean that the service should be modeled as an
asynchronous service, rather than a synchronous one... is it YOUR service
that is giving a 502, or someone elses? If it is someone else's service,
then perhaps contact them and ask them to change it to Async, since it
doesn't sound like a "bug" at all, it's just an incorrectly modeled
service (apparently...??)

Also, if it is a bug, it sounds like a Python API error rather than a Java
API error, so perhaps re-flag it in your bug report.

Cheers!

Mark

> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.1901 / Virus Database: 2109/4696 - Release Date: 12/22/11

[sa...@googlecode.com]

Updates:
Status: Invalid

Comment #1 on issue 13 by elmccar...@gmail.com: sadi.py HTTP 502s when

service takes too long to execute
http://code.google.com/p/sadi/issues/detail?id=13

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.