Re: [NITPICK] didn't see this one coming...
Pier Fumagalli wrote: [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Mon, 29 Apr 2002, Remy Maucherat wrote: However I do think we should somehow document better what's happening - many people have the strange impression that webapp is going to replace jk. I'd like to find a way to indicate that the two preferred connectors are: - Coyote HTTP/1.1 - Coyote JK 2 (AJP with mod_jk, JNI) And to clearly indicate that for whatever OS Pier is using and Apache2, users can also use mod_webapp. I can cover for OS/X and Solaris 8 (both X86 and SPARC). That's all I have access to ATM (my flatmate's Linux box is a happily hand-tuned llama slow Debian box, basically impossible to compile whatever on it) J-F uses a couple of whacko ;) systems, and something else (???) I have some Linux (Suse), access to FreeBSD, Solaris8, ReliantUnix (mips) and BS2000 (EBCDIC mainframe) ;-)) Henri is building RPMs for WebApp already, and since it's another dialect of a pseudo POSIX-compliant OS, things should work there as well, and it's pretty easy to provide fixes when he tries to build the thing. I used to have an HP-UX box as well, but the power supply died last week, and the cost to replace that was much more than the value of the box itself, so it just ended up in the bin with my kitty litter last week... I know that Covalent has some HP-UX boxes, if they want to put them on-line, it might be good (since I was hosting HP-UX for the entire Apache community) Apart from that, if someone wants to do some Windows porting, he's more than welcome to volunteer (as you are well-aware of, it's kinda impossible to run MSVC from remote, you _have_ to have a console. The only alternative would be someone providing a Wintel PC with a valid license of MSVC and an SSH server to do builds on, although it might get nasty when you think about doing all those NMAKE files)... I have (at home) a win98 (For hacking USB devices). I have made some tries there, with cygwin is it possible to run sshd and use a machine remotly. It is even possible to compile programs for native win32. The problem starts when the native program stops and displays a message box (may be vnc can help (http://www.uk.research.att.com/vnc/) but I have not tried it yet) normaly a ps -W + kill -9 or custom shutdown.exe helps... Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
On Mon, 2002-04-29 at 16:15, [EMAIL PROTECTED] wrote: However I do think we should somehow document better what's happening - many people have the strange impression that webapp is going to replace jk. Yep. That was exactly my impression when I started mucking around with connector choices. Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
On Sun, 28 Apr 2002, Bill Barker wrote: Deprecating it was never voted, and the mention should be removed from the documentation. IMO, the issue should then be voted upon. Pre-voting: -1 to deprecate WARP. Now that Pier is back, and interested in maintaining it, WARP deserves an equal chance to compete with AJP. The only positive lesson to come out of the Valve vs. Interceptor holy war was that competition is good. I agree. My problem with mod_webapp as a release manager is that it has many open P1s and P2s nobody seem to care about, as well as many associated frustrated users (because one year later, there's still almost zero documentation). Pier may be back, but he's not fixing bugs either. There's nothing wrong with multiple connectors - and 3.3 still supports mod_jserv ( and I know people who use it ). I think we do agree that coyote will be the connector for http and jk, and we'll include any other component that is actively developed and maintained. As long as Pier and JFC are working on webapp, it'll be alive. However I do think we should somehow document better what's happening - many people have the strange impression that webapp is going to replace jk. I'd like to find a way to indicate that the two preferred connectors are: - Coyote HTTP/1.1 - Coyote JK 2 (AJP with mod_jk, JNI) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
Remy Maucherat [EMAIL PROTECTED] wrote: My problem with mod_webapp as a release manager is that it has many open P1s and P2s nobody seem to care about, We have Severity and Priority ... P1 and P2 do not compute in my vocabulary. Anyway, from 33 to 18 in 10 minutes, not bad, huh? as well as many associated frustrated users (because one year later, there's still almost zero documentation). Wasn¹t to volunteer and write some? Pier may be back, but he's not fixing bugs either. Because from what I can see on the systems I have access to, there are not bugs open... I don't have windows, so I can't fix bugs there. The only one I am kinda concerned about it are 3509, which affects Apache 2.0 as well with the worker MPM, 4930 (file upload is broken _again_), and 6509... So far, anyway, I see only TWO (to use Sun's bug-priority jargon) P1, and those are 3509 and 4930, and the only P2 is 4212 (at least in my priority list)... I'll go ahead and retag all in the bugs DB. Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
On Mon, 29 Apr 2002, Remy Maucherat wrote: However I do think we should somehow document better what's happening - many people have the strange impression that webapp is going to replace jk. I'd like to find a way to indicate that the two preferred connectors are: - Coyote HTTP/1.1 - Coyote JK 2 (AJP with mod_jk, JNI) And to clearly indicate that for whatever OS Pier is using and Apache2, users can also use mod_webapp. ( for 3.3 we do the same for mod_jserv and Apache1.3 ). Note that mod_jk2 is not and will not be ready for 4.1, and JNI doesn't work with 4.x in mod_jk1. PROPOSAL: Rename Coyote-jk2 - coyote-jk. Or just drop the coyote-jk and coyote-http from documentations, no need to confuse users. There is the coyote connector, it supports http/1.1 and mod_jk. The current stable release of mod_jk is mod_jk1.5, the alpha/beta release is mod_jk2. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
On Mon, 29 Apr 2002, Remy Maucherat wrote: However I do think we should somehow document better what's happening - many people have the strange impression that webapp is going to replace jk. I'd like to find a way to indicate that the two preferred connectors are: - Coyote HTTP/1.1 - Coyote JK 2 (AJP with mod_jk, JNI) And to clearly indicate that for whatever OS Pier is using and Apache2, users can also use mod_webapp. I suppose. And where do I put that in the docs ? In the release notes maybe ? ( for 3.3 we do the same for mod_jserv and Apache1.3 ). Note that mod_jk2 is not and will not be ready for 4.1, and JNI doesn't work with 4.x in mod_jk1. Yes, I did know that. When it is ready, it should be possible to distribute it independently, right ? (separate binary) PROPOSAL: Rename Coyote-jk2 - coyote-jk. Or just drop the coyote-jk and coyote-http from documentations, no need to confuse users. There is the coyote connector, it supports http/1.1 and mod_jk. Yes, I suppose it's one connector supporting many protocols, so maybe it would be a good idea to do that, call the thing Coyote and merge the two pages (esp since there is little HTTP/1.1 docs needed). Or make one main page with sub-pages. I had a question about the autoconfiguration with JK 2. Is it the same as in JK 1 ? If it's not, a large part of the documentation is stale. The current stable release of mod_jk is mod_jk1.5, the alpha/beta release is mod_jk2. Ok. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Mon, 29 Apr 2002, Remy Maucherat wrote: However I do think we should somehow document better what's happening - many people have the strange impression that webapp is going to replace jk. I'd like to find a way to indicate that the two preferred connectors are: - Coyote HTTP/1.1 - Coyote JK 2 (AJP with mod_jk, JNI) And to clearly indicate that for whatever OS Pier is using and Apache2, users can also use mod_webapp. I can cover for OS/X and Solaris 8 (both X86 and SPARC). That's all I have access to ATM (my flatmate's Linux box is a happily hand-tuned llama slow Debian box, basically impossible to compile whatever on it) J-F uses a couple of whacko ;) systems, and something else (???) Henri is building RPMs for WebApp already, and since it's another dialect of a pseudo POSIX-compliant OS, things should work there as well, and it's pretty easy to provide fixes when he tries to build the thing. I used to have an HP-UX box as well, but the power supply died last week, and the cost to replace that was much more than the value of the box itself, so it just ended up in the bin with my kitty litter last week... I know that Covalent has some HP-UX boxes, if they want to put them on-line, it might be good (since I was hosting HP-UX for the entire Apache community) Apart from that, if someone wants to do some Windows porting, he's more than welcome to volunteer (as you are well-aware of, it's kinda impossible to run MSVC from remote, you _have_ to have a console. The only alternative would be someone providing a Wintel PC with a valid license of MSVC and an SSH server to do builds on, although it might get nasty when you think about doing all those NMAKE files)... Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
On Mon, 29 Apr 2002, Remy Maucherat wrote: Yes, I suppose it's one connector supporting many protocols, so maybe it would be a good idea to do that, call the thing Coyote and merge the two pages (esp since there is little HTTP/1.1 docs needed). Or make one main page with sub-pages. Porbably so - for the java side and server.xml there is no reason to confuse people. There is one connector - that's it. Probably even 'coyote' can be removed from the docs :-) - if we agree ( and so far it seems we do ) that Coyote is going to be the default connector ( and I believe we can get a majority for both 4.0 and 3.3 to support that ) - then it'll be just that, 'the' connector. That doesn't mean the others are not supported - just that we recommend one default. I had a question about the autoconfiguration with JK 2. Is it the same as in JK 1 ? If it's not, a large part of the documentation is stale. Yes, using the same code - I can move the config generator from o.a.ajp - but it's better to let people use the same class names. The autoconfig generates mod_jk1 config ( JkMount, etc ). For mod_jk2 the config is different, and a different autoconf will be used ( I'll send a proposal in the next mail ). Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
On Mon, 29 Apr 2002, Pier Fumagalli wrote: As long as we find and fix the docs that sugest that mod_webapp is 'replacing' mod_jk and is the 'default' Apache2 ( or whatever) connector - I'm fine. I heard many people who believe that - and it is certainly not the case. Costin [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Mon, 29 Apr 2002, Remy Maucherat wrote: However I do think we should somehow document better what's happening - many people have the strange impression that webapp is going to replace jk. I'd like to find a way to indicate that the two preferred connectors are: - Coyote HTTP/1.1 - Coyote JK 2 (AJP with mod_jk, JNI) And to clearly indicate that for whatever OS Pier is using and Apache2, users can also use mod_webapp. I can cover for OS/X and Solaris 8 (both X86 and SPARC). That's all I have access to ATM (my flatmate's Linux box is a happily hand-tuned llama slow Debian box, basically impossible to compile whatever on it) J-F uses a couple of whacko ;) systems, and something else (???) Henri is building RPMs for WebApp already, and since it's another dialect of a pseudo POSIX-compliant OS, things should work there as well, and it's pretty easy to provide fixes when he tries to build the thing. I used to have an HP-UX box as well, but the power supply died last week, and the cost to replace that was much more than the value of the box itself, so it just ended up in the bin with my kitty litter last week... I know that Covalent has some HP-UX boxes, if they want to put them on-line, it might be good (since I was hosting HP-UX for the entire Apache community) Apart from that, if someone wants to do some Windows porting, he's more than welcome to volunteer (as you are well-aware of, it's kinda impossible to run MSVC from remote, you _have_ to have a console. The only alternative would be someone providing a Wintel PC with a valid license of MSVC and an SSH server to do builds on, although it might get nasty when you think about doing all those NMAKE files)... Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Mon, 29 Apr 2002, Pier Fumagalli wrote: As long as we find and fix the docs that sugest that mod_webapp is 'replacing' mod_jk and is the 'default' Apache2 ( or whatever) connector - I'm fine. I don't think it even exists. AFAICR I never wrote anything like that. Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
context file=/webapps/tomcat-docs/config/webapp.xml pbIMPORTANT NOTE: The Webapp connector is now deprecated. Use the Coyote JK 2 connector instead./b/p /context I'm just asking why??? Just because it doesn't use Coyote? Deprecating it was never voted, and the mention should be removed from the documentation. IMO, the issue should then be voted upon. Only disabling it from the default configuration was voted upon. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
Deprecating it was never voted, and the mention should be removed from the documentation. IMO, the issue should then be voted upon. Pre-voting: -1 to deprecate WARP. Now that Pier is back, and interested in maintaining it, WARP deserves an equal chance to compete with AJP. The only positive lesson to come out of the Valve vs. Interceptor holy war was that competition is good. Only disabling it from the default configuration was voted upon. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [NITPICK] didn't see this one coming...
On Sun, 28 Apr 2002, Bill Barker wrote: Deprecating it was never voted, and the mention should be removed from the documentation. IMO, the issue should then be voted upon. Pre-voting: -1 to deprecate WARP. Now that Pier is back, and interested in maintaining it, WARP deserves an equal chance to compete with AJP. The only positive lesson to come out of the Valve vs. Interceptor holy war was that competition is good. I agree. There's nothing wrong with multiple connectors - and 3.3 still supports mod_jserv ( and I know people who use it ). I think we do agree that coyote will be the connector for http and jk, and we'll include any other component that is actively developed and maintained. As long as Pier and JFC are working on webapp, it'll be alive. However I do think we should somehow document better what's happening - many people have the strange impression that webapp is going to replace jk. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[NITPICK] didn't see this one coming...
context file=/webapps/tomcat-docs/config/webapp.xml pbIMPORTANT NOTE: The Webapp connector is now deprecated. Use the Coyote JK 2 connector instead./b/p /context I'm just asking why??? Just because it doesn't use Coyote? Pier -- I think that it's extremely foolish to name a server after the current U.S. President. B.W. Fitzpatrick -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
