Re: Converting Coyote to Java2 collections
Bill Barker wrote: As long as they go back to j-t (esp. Expirer & Reaper), I'm +1. I can leave those two classes, no problem. It's not as if they were really big. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Converting Coyote to Java2 collections
As long as they go back to j-t (esp. Expirer & Reaper), I'm +1. - Original Message - From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, February 03, 2004 5:14 AM Subject: Re: Converting Coyote to Java2 collections Bill Barker wrote: > I suppose that Coyote can be optional for TC 3.3. I'm a bit less > comfortable on using them in o.a.t.u (since that would force a Java2 > requirement on 3.3). Stuff I'm considering for removal: - o.a.t.util.collections (except MultiMap - which might as well be merged into Parameters, BTW) - o.a.t.util.log (except SLH and CL) - o.a.t.util.mx (experiments for commons-modeler) - o.a.t.util.threads: Epirer, Reaper, ThreadPoolMX Of course, I'm only using TC 5, so ... ;) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Converting Coyote to Java2 collections
Bill Barker wrote: I suppose that Coyote can be optional for TC 3.3. I'm a bit less comfortable on using them in o.a.t.u (since that would force a Java2 requirement on 3.3). Stuff I'm considering for removal: - o.a.t.util.collections (except MultiMap - which might as well be merged into Parameters, BTW) - o.a.t.util.log (except SLH and CL) - o.a.t.util.mx (experiments for commons-modeler) - o.a.t.util.threads: Epirer, Reaper, ThreadPoolMX Of course, I'm only using TC 5, so ... ;) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Converting Coyote to Java2 collections
If you want to move o.a.t.u.log back to j-t, I've got no objection. I don't think that anybody is using o.a.t.u.handler. - Original Message - From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Monday, February 02, 2004 1:03 PM Subject: Re: Converting Coyote to Java2 collections Bill Barker wrote: > I suppose that Coyote can be optional for TC 3.3. I'm a bit less > comfortable on using them in o.a.t.u (since that would force a Java2 > requirement on 3.3). The thing which was annoying me the most was the attributes Hashtable in the request. I think util is using mostly custom structures for GC and speed. There's also deprecated stuff in util (logging, etc). Should this also be left in for compatibility ? Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Converting Coyote to Java2 collections
Bill Barker wrote: I suppose that Coyote can be optional for TC 3.3. I'm a bit less comfortable on using them in o.a.t.u (since that would force a Java2 requirement on 3.3). The thing which was annoying me the most was the attributes Hashtable in the request. I think util is using mostly custom structures for GC and speed. There's also deprecated stuff in util (logging, etc). Should this also be left in for compatibility ? Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Converting Coyote to Java2 collections
I suppose that Coyote can be optional for TC 3.3. I'm a bit less comfortable on using them in o.a.t.u (since that would force a Java2 requirement on 3.3). - Original Message - From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Monday, February 02, 2004 11:54 AM Subject: Converting Coyote to Java2 collections Are there any big complaints if I convert Coyote to use Java2 collections ? (less sync) Or is the pure JDK 1.1 compatibility still a big plus ? Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Converting Coyote to Java2 collections
no complaints here :) just be careful of those ConcurrentModificationException(s) that are lurking in the iterators :-) Filip -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Monday, February 02, 2004 11:54 AM To: Tomcat Developers List Subject: Converting Coyote to Java2 collections Are there any big complaints if I convert Coyote to use Java2 collections ? (less sync) Or is the pure JDK 1.1 compatibility still a big plus ? Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]