On Thu, 2010-09-09 at 14:35 +0000, Sujit Basu wrote: > Hi, > I'm developing a HTTP Client application with some key requirements, which > are as following (I'm also putting some inline notes/questions): > 1. HTTPS with mutual SSL Authentication using certificates.Note: I have used > Commons HttpClient v4.0.1 successfully in the recent past to do this type of > SSL Certificate Authentication. > 2. Use a single persistent HTTPS connectionQ: Using a connection manager with > max connection=1 is better than using a no explicit connection manager?
It depends. If you want to have no more than connection per host but intend to access those hosts concurrently from multiple threads you should be using a pooling connection manager. If you want no more than one connection at any point of time, the default connection manager is your best choice. > 3. The client needs to poll the connection to check for new responses. The > server will be using a COMET type message exchange, where it can push message > to the client, without receiving an explicit request from the client.Q: Is > HttpCore NIO is a good starting point to build this functionality? Q: Is > there a way for HttpClient to poll the connection for new responses? > Any suggestion/advice for a good starting point HttpClient/HttpCore? and even > Sample code (particularly for HttpCore NIO, if suggested) will be highly > appreciated. HttpCore NIO should probably the best starting point. You must be prepared to write custom protocol handlers, though. Examples of standard HTTP protocol handlers can be found here: http://hc.apache.org/httpcomponents-core-ga/examples.html HttpCore tutorial can be found here: http://hc.apache.org/httpcomponents-core-ga/tutorial/html/index.html Hope this helps Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
