hakan.jacobsson wrote:
Oleg,
First option is recommended if we upgrade to 4.0 I take it? Is it a
stable release or beta?
No, the third option is still preferred, in my opinion.
HttpClient 4.0 is considered BETA. That did not, however, prevent Google
from including it into its Android platform.
Third option, could you please explain it in some more detail, I don't
get it.=/
As far as I understand the main objective is to ensure the retrieval of
content of an ad does not block for too long thus preventing the server
from sending a response back to the client in a timely manner. So,
instead of retrieving content of the ad synchronously, respond to the
client without blocking and make the browser download the content of the
ad asynchronously, either using AJAX or an iframe.
Hope this helps
Oleg
/regards, Håkan
19 jan 2009 kl. 19.50 skrev Oleg Kalnichevski:
You have three options:
(1) Recalculate (decrease) the SO_TIMEOUT value after each successful
read from the input stream. Not recommended unless you are willing to
upgrade to HttpClient 4.0
(2) Start a controller thread that aborts the request if it has not
completed to a specific deadline. Not recommended unless the number of
requests is relatively small.
(3) Reconsider the requirements (for instance, retrieve content
asynchronously instead of enforcing a total timeout on the requests).
Recommended.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
