the timeout is for the connection. okclients have 3 timeouts available (connection, read, write).
they can all be set individually, but i do not believe the implementation that we use does this.
the connection timeout defintely works, so your statement to the contrary is not correct. it's doing
what it's supposed to do, just not what you want it to do.
i have a small okhttp client which i have used to test the various timeouts. it is possible to set a
read timeout independently of a connection timeout and cause timeout exceptions for each. for
your case use, you might have to write a java routine or possibly a javaobject wrap from b4a. you
might be able to incorporate it into okhttputils. i don't know how determined you are to make it
work like you want.