Hi there, >> RESOLVED, that the Apache !HttpComponents Project will not create new >> applications, but only '''adopt existing efforts''' at Apache to >> develop >> applications based on the components and wishing to join the Apache >> !HttpComponents Project, '''excluding''' efforts to implement >> '''standardized server-side containers''' such as a Servlet or Portlet >> container; and be it further
From my (a bit of an outsider's) point of view, the "develop applications based on the components" bit in it (and the surrounding paragraph) has a bit of a weakening effect on the definition and the direction of the project. 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? Why not make exactly that the mission of the project? It then becomes very clear what the project is about. To you AND to the public. Wouldn't adopting existing efforts or applications blur the focus, fog the priorities? If there there are other activities, not falling in this area, they could always be made separate projects, no? Do not get me wrong -- obviously I am not writing this to tell you what to do, but just to give some feedback from someone 'of the rest of the world'. And thanks for putting your time into HTTP core. Seems to be doing a fine job. Cheers, Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
