Hi all,
I was wondering if there is a way to retrieve the Socket (and therefore the
SSLSession if using SSL) from a connection.
I noticed there is a protected getSocket() method in the HttpConnetion
class, but since this method is protected and not public it is no good for
me (or can I somehow
On Wed, Jun 03, 2009 at 03:00:31PM +0200, Guy wrote:
Hi all,
I was wondering if there is a way to retrieve the Socket (and therefore the
SSLSession if using SSL) from a connection.
I noticed there is a protected getSocket() method in the HttpConnetion
class, but since this method is
Hi,
We are using HTTP-NIO 4.0 to communicate with our internal http servers, on a
very high volume bases (80Mbits/second on both upload and download). We use
AsyncNHttpClientHandler and DefaultClientIOEventDispatch.
We are seeing some strange behaviors randomly. After putting some debug
Hello Oleg,
Do you know any idea about when you plan to release H4-beta3?
Many thanks,
Joan.
Hi Oleg,
I noticed that the currently-downloadable HttpClient 4.0-beta2 relies on the
non-final beta release of HttpCore 4.0 (httpcore-4.0-beta3). It seems wasteful
not to take advantage of the *final* core version now that it's available, so I
looked at the svn repos for HttpClient:
Yongxing Wang wrote:
Hi,
We are using HTTP-NIO 4.0 to communicate with our internal http servers, on a very high volume bases (80Mbits/second on both upload and download). We use AsyncNHttpClientHandler and DefaultClientIOEventDispatch.
We are seeing some strange behaviors randomly. After
Joan Balagueró Valls wrote:
Hello Oleg,
Do you know any idea about when you plan to release H4-beta3?
Many thanks,
Joan.
Hi Joan
HttpClient 4.0 trunk has been quite stable so far (7 bug fixed since
beta4, only one of which I would consider anywhere near major).
Therefore
Will McQueen wrote:
Hi Oleg,
I noticed that the currently-downloadable HttpClient 4.0-beta2 relies on the
non-final beta release of HttpCore 4.0 (httpcore-4.0-beta3). It seems wasteful
not to take advantage of the *final* core version now that it's available, so I
looked at the svn repos for
Using 3.1
I cannot seem to get wire logging to produce anything in my log.
Here is the code:
FileHandler defaultHandler = new FileHandler(path + BBD%u.log, 5,
1, true);
Logger.getLogger().addHandler(defaultHandler);
Danny,
On Wed, Jun 3, 2009 at 13:53, Danny Gallagher
danny.gallag...@generatedsystems.com wrote:
Using 3.1
I cannot seem to get wire logging to produce anything in my log.
Here is the code:
FileHandler defaultHandler = new FileHandler(path + BBD%u.log, 5,
1, true);
Bindul,
Thanks, sometimes even if the problem is staring you right in the face, you
can't see it.
I removed the .level from the logger names.
Still no logging of data over the wire.
I've tried various ways of setting up the logging, passing as JVM options,
setting in the
Bindul,
Thanks, sometimes even if the problem is staring you right in the
face, you can't see it.
I removed the .level from the logger names.
Still no logging of data over the wire.
I've tried various ways of setting up the logging, passing as JVM options,
setting in the
12 matches
Mail list logo