I'm considering using the latest NIO HttpCore code and I'd like to get a rough idea of how stable it is for the use case described below. The basic question is: Would you feel comfortable basing a heavily used production system on it at this time, if you were willing to do some debugging of problems?
My application currently uses HttpClient 3.x to connect to thousands of different HTTP servers over SSL (not all at once). The system POSTs 4K to 10K of data to a server after authenticating using basic auth. The reason for considering the switch to NIO HttpCore is to improve performance. Under heavy load, when the servers fielding the POSTs become slow, threads stay blocked for too long and the system runs out of threads doing useful work. The current system does not stay connected to an HTTP server between requests. Doing so might improve things, since some servers need to be sent many more messages than others. The servers fielding the POSTs are implemented using a variety of different HTTP server software. The program sending the POSTs is heavily loaded. Is the NIO HttpCore currently stable enough to try using for an application like this? What sort of problems am I likely to encounter? Thanks very much. bob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
