Re: [HttpCore] EntityDeserializer and EntitySerializer public interfaces

2006-11-08 Thread Roland Weber
Hi Oleg, With all the latest changes in HttpCore I no longer think that pluggable EntityDeserializer and EntitySerializer represent any real value. They just clutter the API. One can still override #receive/sendRequestEntity #send/receiveResponseEntity methods of the default client / server

Re: [HttpCore] EntityDeserializer and EntitySerializer public interfaces

2006-11-08 Thread Oleg Kalnichevski
On Wed, 2006-11-08 at 17:33 +0100, Roland Weber wrote: Hi Oleg, With all the latest changes in HttpCore I no longer think that pluggable EntityDeserializer and EntitySerializer represent any real value. They just clutter the API. One can still override #receive/sendRequestEntity

How to ensure socket reuse on client side?

2006-11-08 Thread umesh409
I am new to HttpCore and using 4.0 Alpha 2 version. I am trying to connect a server and request more than one pages from that server using the same connection. My goal is to reuse socket so that no new socket is opened on the Http client for the subsequent requests to the same server and port.

Re: How to ensure socket reuse on client side?

2006-11-08 Thread Oleg Kalnichevski
On Thu, 2006-11-09 at 04:46 +0800, [EMAIL PROTECTED] wrote: I am new to HttpCore and using 4.0 Alpha 2 version. I am trying to connect a server and request more than one pages from that server using the same connection. My goal is to reuse socket so that no new socket is opened on the Http