[ANNOUNCEMENT][HttpClient] HttpClient 2.x end of life
The HttpClient 2.x codebase is hereby declared end of life. This means: * The HttpClient 2 code base is officially unmaintained (dormant) * There will be no more HttpClient 2.x releases * The HttpClient 2.0 site will be taken offline as soon as the HttpCompontents site is set up. Community support is of course still available through the mailing lists. We strongly recommend all our users to move to the current stable version 3.0: http://jakarta.apache.org/commons/httpclient/ See http://vmgump.apache.org/gump/public/commons-httpclient-20-branch/commons-httpclient-2.0-branch/details.html for a list of dependent projects. The project team is now focussing on development of the codebase for HttpComponents which will eventually produce HttpClient 4. - Ortwin Glück - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] Naming for new Jakarta subproject
I'd also prefer a one-word catchy name to something uber-geeky like Web Components, so if we really can't use Silk we can come up with some other options and have a new vote... Yoav On 2/27/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: I've come to understand that a name Apache FOO does not violate the trademark FOO. As such, I don't think there's any problem with Apache Silk. Sanjiva. On Mon, 2006-02-27 at 00:49 -0500, Henri Yandell wrote: On Sun, 21 Aug 2005, Henri Yandell wrote: Apache Silk it is: [17]Apache Silk [ 0]Apache Web Bricks [ 0]Apache Web Commons (branding issue with Commons) [ 3]Apache Web Components [ 0]Apache Web Parts (conflict with Microsoft and sf.net) 20 +1 votes with 1 abstainer. So now we can finish the proposal, get it voted on and start with the fun stuff. Okay. I've been unable to get this resolved - for the following reasons: * Segue's SilkXxx web testing suite seems to clash on the trademark. * General lack of response on PRC on the trademark issue. We lack decision making on the grey line at the moment - but after having this sit on the back burner for many months I'm of the opinion that we clash too much with the Segue trademark. * Jakarta Web Components matches Jakarta Http Components in pattern and fits the proposals I've made on restructuring Jakarta (ie: they're both groupings). So I'd like to suggest we go ahead with Jakarta Web Components. Any thoughts? And sorry for taking so long to bring this up, it's been on my todo list since ApacheCon. Hen - 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] -- Yoav Shapira System Design and Management Fellow MIT Sloan School of Management Cambridge, MA, USA [EMAIL PROTECTED] / www.yoavshapira.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] Naming for new Jakarta subproject
I'm in favour of boring as I'm pushing for a Jakarta made up of components, and not sub-projects. Http Components, Web Components would just be groupings of components to improve the information architecture of the site/mail-lists/whatever where necessary. Catchy names would be used for the components, not groupings. Hen On Mon, 27 Feb 2006, Yoav Shapira wrote: I'd also prefer a one-word catchy name to something uber-geeky like Web Components, so if we really can't use Silk we can come up with some other options and have a new vote... Yoav On 2/27/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: I've come to understand that a name Apache FOO does not violate the trademark FOO. As such, I don't think there's any problem with Apache Silk. Sanjiva. On Mon, 2006-02-27 at 00:49 -0500, Henri Yandell wrote: On Sun, 21 Aug 2005, Henri Yandell wrote: Apache Silk it is: [17]Apache Silk [ 0]Apache Web Bricks [ 0]Apache Web Commons (branding issue with Commons) [ 3]Apache Web Components [ 0]Apache Web Parts (conflict with Microsoft and sf.net) 20 +1 votes with 1 abstainer. So now we can finish the proposal, get it voted on and start with the fun stuff. Okay. I've been unable to get this resolved - for the following reasons: * Segue's SilkXxx web testing suite seems to clash on the trademark. * General lack of response on PRC on the trademark issue. We lack decision making on the grey line at the moment - but after having this sit on the back burner for many months I'm of the opinion that we clash too much with the Segue trademark. * Jakarta Web Components matches Jakarta Http Components in pattern and fits the proposals I've made on restructuring Jakarta (ie: they're both groupings). So I'd like to suggest we go ahead with Jakarta Web Components. Any thoughts? And sorry for taking so long to bring this up, it's been on my todo list since ApacheCon. Hen - 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] -- Yoav Shapira System Design and Management Fellow MIT Sloan School of Management Cambridge, MA, USA [EMAIL PROTECTED] / www.yoavshapira.com - 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]
Re: [RESULT] Naming for new Jakarta subproject
Problem is, you're the only person who's come out and said that. Cliff's not looked into the legalities of trademarks yet and no one on the PRC had a yes/no answer. Hen On Mon, 27 Feb 2006, Sanjiva Weerawarana wrote: I've come to understand that a name Apache FOO does not violate the trademark FOO. As such, I don't think there's any problem with Apache Silk. Sanjiva. On Mon, 2006-02-27 at 00:49 -0500, Henri Yandell wrote: On Sun, 21 Aug 2005, Henri Yandell wrote: Apache Silk it is: [17]Apache Silk [ 0]Apache Web Bricks [ 0]Apache Web Commons (branding issue with Commons) [ 3]Apache Web Components [ 0]Apache Web Parts (conflict with Microsoft and sf.net) 20 +1 votes with 1 abstainer. So now we can finish the proposal, get it voted on and start with the fun stuff. Okay. I've been unable to get this resolved - for the following reasons: * Segue's SilkXxx web testing suite seems to clash on the trademark. * General lack of response on PRC on the trademark issue. We lack decision making on the grey line at the moment - but after having this sit on the back burner for many months I'm of the opinion that we clash too much with the Segue trademark. * Jakarta Web Components matches Jakarta Http Components in pattern and fits the proposals I've made on restructuring Jakarta (ie: they're both groupings). So I'd like to suggest we go ahead with Jakarta Web Components. Any thoughts? And sorry for taking so long to bring this up, it's been on my todo list since ApacheCon. Hen - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
http://tomcat.apache.org/connectors-doc/howto/quick.html Typo
I just noticed there is a typo on the page: http://tomcat.apache.org/connectors-doc/howto/quick.html Under the minimum workers.properties section worker.worker1.reclycle_timeout=300 should be worker.worker1.recycle_timeout=300 (recycle is misspelled) Maybe not a big issue, but for newbies like me who cut and paste it might solve some issues. -- Tom Beighley www.TomTheGeek.com
Re: http://tomcat.apache.org/connectors-doc/howto/quick.html Typo
Tom Beighley wrote: I just noticed there is a typo on the page: http://tomcat.apache.org/connectors-doc/howto/quick.html Under the minimum workers.properties section worker.worker1.reclycle_timeout=300 should be worker.worker1.recycle_timeout=300 (recycle is misspelled) Maybe not a big issue, but for newbies like me who cut and paste it might solve some issues. Thanks Tom. Fixing it now... Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
