Is this a common problem? Perhaps the Apache HTTPClient people know about it. Do URLConnectionClient and/or HttpClient4 have the same problem?
I'm willing to develop a decorator for net.oauth.http.HttpClient that implements a time limit using an executor and a future. But I'd rather find a way to make the Apache HTTPClient 3 work. On Jul 27, 7:10 pm, Zhihong <[email protected]> wrote: > I found that these timeout values don't work sometimes with HTTPClient > 3. We had a failcase that connection timeout is several minutes when > firewall blocks the request. > > If this problem is widespread, it may be a good idea to add an option > to run the request in a timer-thread using the technique mentioned by > Paul. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
