-
Notifications
You must be signed in to change notification settings - Fork 31
Open
Description
Synchronous requests don't have a proper timeout argument.
What steps will reproduce the problem?
1. use python's example/time
(fix paths if needed)
2. change run_server.py to sleep 10 seconds just before returning
time.sleep(10)
done.run(response)
3. execute run_server.py
4. execute run_client.py (using 1 second timeout)
What is the expected output? What do you see instead?
we expect an exception like
RpcError('request timed out')
instead the request completes successfully (after ~10 seconds)
What version of the product are you using? On what operating system?
protobuf-socket-rpc 1.3.2, linux
the Java API doesn't even seem to have a timeout parameter.
Please provide any additional information below.
ideally all client APIs, python and java, will have a timeout
parameter in all synchronous calls. all requests should fail with
a timeout-exception if the request is not completed withing the
specified timeout, for _any_ reason, including
- connection timeout
- slow server
- suspended server
etc.
Original issue reported on code.google.com by boaz.kel...@gmail.com on 29 Jun 2011 at 7:02
Reactions are currently unavailable