Hello, I am contacting you on behalf of the Apache ManifoldCF project. This project consists of a crawler framework plus a number of prebuilt connectors to various repositories and output indexes.
I've recently looked at using Apache CXF as a replacement for Axis for development of new web-services based connectors. Everything has been going well until I realized that CXF seemingly takes away all control over connection pooling from the user. This is inconsistent with the ManifoldCF model, unfortunately, where the connectors have user-configured maximum numbers of outstanding connections for every kind of connection. The specific model required by ManifoldCF is as follows: each connection instance is set up by the framework, and is expected to maintain at most one connection to the service. The connections will be used when needed, by the framework, and explicitly closed when idle long enough (at the control of the connector writer), or explicitly closed, once again by the framework. For all of our projects using Web Services or HTTP in the past, we've used HttpComponents/HttpClient, and had each connection set up its own connection pool of size 1. This has all the right characteristics. Is there any way to implement this model programmatically using the AsyncHTTPConduit? If not, is there any way I can easily create my own conduit implementation that would allow such pool management? (Otherwise, the Async conduit appears to have everything I need, although it's a bit clunky to configure.) Thanks in advance, Karl
