On Wed, Jul 22, 2009 at 06:41:26PM -0400, Peter Soles wrote:
I checked the archives of the list - coudn't find the answer to my
question. Apologies if I missed something.
I'm writing a simulator that will simulate many clients long polling the
same server. The server requires SSL so I'm
Thanks for the response. I am using 4.0.1 of HttpCore.
I looked a little more into it and found that the number of requests and
responses is dependent on the server I am contacting. For example, I tried
pointing the code to the gmail login page and got many more than 100
request/response pairs.
Peter Soles wrote:
Thanks for the response. I am using 4.0.1 of HttpCore.
I looked a little more into it and found that the number of requests and
responses is dependent on the server I am contacting. For example, I
tried pointing the code to the gmail login page and got many more than
100
Thanks Oleg - I guess I goofed in my understanding of how the handler works.
Need to read the tutorial (again!). I would definitely like to use a
connection manager to reuse the connection.
It's working great now! Thanks again for the help.
Peter
On Thu, Jul 23, 2009 at 5:17 PM, Oleg
Pressed send too soon:
SSLSocketFactory is not inherently thread-safe, because of the
[gs]etHostNameVerifier() methods.
Is there a need to change the HostNameVerifier after construction, or
could the verifier be provided to the ctor? Alternatively, perhaps the
field could be made volatile?
On