Hello Jörg, thanks for your feedback.
>_Listening in to the discussion on this list and checking out the web pages, >_my impression is you guys are writing the HTTP core components, a set of lean >_and clean low level components for implementing HTTP based services (please >_read services not in the strict SOAP sense). >_ >_Isn't that cool enough? Cool enough for me. But it's not like the developers are lining up to join us either. >_If there there are other activities, not falling in this area, they could >_always be made separate projects, no? No, not always. See the JMeter related discussions in this thread. Also, there were discussions a few months back about joining with Slide. Slide has a client side that could become a component, but it also has a server side which never ever will pass as being a "component". Not that it matters much, since Slide::server is and will remain dead. >From my point of view, those are two valid suggestions we could not adopt if our scope is "components only". The benchmark contrib code is also used, and it has been suggested to put it in a JAR at least. That is more of an application than a component, too. But that's only my personal view, of course. If others feel better without the application part, I'm not going to insist on it. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
