On Sun, 2007-03-11 at 11:31 +0100, Roland Weber wrote: > Hi Oleg, > > > With all due respect I do not see it this way. Ability to queue requests > > is the only thing I can think of, which HttpCore NIO has and HttpCore > > CIO does not. > > If you consider ElementalHttpServer as part of HttpCore, I can see your > point. If I am not mistaken, NIO includes logic to dispatch incoming > requests to worker threads. That's nowhere in the module-main JAR. We > give an example of how to do it, but NIO builds a framework. I guess > multithreading is inseparable from NIO and can rightfully claim to be > at the core for NIO, so I'll shut up on this matter. > > >> From what little I know of Maven, it should not be too > >> tricky to create a meta release of HttpComponents by > >> unjaring the individual modules and rejaring them into > >> a single package. If we had that, we could ask users > >> (in particular Synapse) to build against that for > >> convenience. The meta release would be synchronized > >> with releases of the individual components, in three > >> flavors: > >> HttpComponents-early packages the newest release of > >> everything, whether it be alpha, beta, RC or final. > >> HttpComponents-mature packages only mature releases, > >> that is (beta?,) RC and final. > >> HttpComponents-final packages only final releases. > >> > > > > I am afraid this approach will break Maven's dependency mediation and > > conflict resolution mechanism [1], which presently assumes one version > > per artifact (JAR). If we ever provide HttpComponents bundle, it should > > be clearly targeted at non-Maven users who prefer to manage project > > dependencies manually. > > > > [1] > > > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > > Transitive dependencies? You mean it's a simple as defining a dummy > artefact with all the alphas as a dependency and then those alphas > will be picked up as transitive dependencies by everyone depending > on the dummy? HttpClient (+Maven) users will declare only HttpClient > as a dependency and automatically pick up HttpCore and, if we should > have them, HttpAuth and HttpCookie? Regardless of whether they are > a module of HttpClient or a separate component? Synapse is going to > depend on module-niossl and will get HttpCore and HttpNIO without > noticing where they come from?
Hi Roland, I believe this is correct. > That sounds promising. Dummy artefacts for Maven users, > repackaged JARs for manual deployment. > Yep. We would still have to get a formal okay from the rest of Jakarta to go ahead with this approach, though. I can start working on a proposal once HttpClient 3.1rc1 and HttpCore 4.0a4 have been released, HttpConn reviewed, Not-Yet-Commons SSL proposal commented on, HttpAuth ported to the new API, and Axis2 simple HTTP server updated to HttpCore 4.0a4 ;-) Oleg > cheers, > Roland > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
