RE: connector status in tomcat 4
>> >Ok. Is there any written specification för the ajp protocol >adn where can I >find it? You could find both ajp13 and ajp14 protocol documentation in at least : jakarta-tomcat-connectors/jk/src/doc/
Re: connector status in tomcat 4
Erik Hellman wrote: > > > -Original Message- > > From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] > > > > >What is it that the connector has to be able to do? Is it > > >sufficient if it > > >simply can forward the HTTP request to tomcat or does it need > > >to play around > > >with it? I guess it must do something or the disscusion on ajp13/jk and > > >warp/webapp wouldn't be. > > > > The web-server connector forward request to tomcat and add some > > information, like the SESSION-COOKIES. In return the tomcat add > > a var, jvmroute, which is used in load-balancing config to be sure > > that the same tomcat will serve the next queries for that session. > > > I guess that with information you mean all the HTTP-headers in the request > and "forward request" is the parameters in the POST or GET (or any of the > other HTTP commands). > basically, all of the request information is passed from the web server to tomcat via the protocol. that includes headers, query string, post data, etc.. > > The connector use a simple protocol, ajp12/13/14, to forward the > > request. You may imagine a web-connector forwarding the request > > using HTTP protocol, but this one is more complex to handle. > > > Ok. Is there any written specification för the ajp protocol adn where can I > find it? > http://jakarta.apache.org/tomcat/tomcat-3.3-doc/AJPv13.html http://jakarta.apache.org/cvsweb/index.cgi/jakarta-tomcat-connectors/jk/src/doc/AJPv14.txt > // Erik
RE: connector status in tomcat 4
> -Original Message- > From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] > > >What is it that the connector has to be able to do? Is it > >sufficient if it > >simply can forward the HTTP request to tomcat or does it need > >to play around > >with it? I guess it must do something or the disscusion on ajp13/jk and > >warp/webapp wouldn't be. > > The web-server connector forward request to tomcat and add some > information, like the SESSION-COOKIES. In return the tomcat add > a var, jvmroute, which is used in load-balancing config to be sure > that the same tomcat will serve the next queries for that session. > I guess that with information you mean all the HTTP-headers in the request and "forward request" is the parameters in the POST or GET (or any of the other HTTP commands). > The connector use a simple protocol, ajp12/13/14, to forward the > request. You may imagine a web-connector forwarding the request > using HTTP protocol, but this one is more complex to handle. > Ok. Is there any written specification för the ajp protocol adn where can I find it? // Erik
RE: connector status in tomcat 4
>GOMEZ Henri at [EMAIL PROTECTED] wrote: > >>> In that case, what is the point of warp. Is it going to be >>> faster, more scalable or something? >> >> warp is a whole new developpement using >> very recent lib tools like APR. >And a bunch of other features and improvements, but it seems >that no one >ever listen to what I write - technically speaking :) :) :) :) What's the technicals improvements apart of the use of APR, technically speaking ? >>> If not why was it created? >> >> That's a good question and who has the answer ? > >I do, and the mailing list archive... Check out for subjects >like WARP :) The first time we saw something about Warp is in the announcement of Tomcat 4.0 m4. I couldn't find any discussion on tomcat-dev (or tomcat-user) about starting a new connector (mod_webapp) instead adding features to ajp13 and using mod_jk ;( Could help me find the initial thread on mod_webapp/warp ?) Regards => List: tomcat-dev Subject: Tomcat 4.0 Milestone 4 From: "Craig R. McClanahan" <[EMAIL PROTECTED]> Date: 2000-11-01 0:09:41 [Download message RAW] Hey folks, I'm planning on cutting a fourth milestone of Tomcat 4.0 tomorrow (Wednesday) evening. This milestone will reflect all of the changes that occurred in the servlet 2.3 and JSP 1.2 specifications between public draft and proposed final draft (and there were a *bunch* of them), completion of the remaining new 2.3/1.2 functionality, and several bug fixes. This will be the last big push of spec-related functionality additions for Tomcat 4.0. Now, we can turn our attention more towards bug fixes and performance tuning. You can help in that process by downloading and playing with the Tomcat 4.0 milestone. I'd like to see us shake it out enough to be production quality by Christmas time. Besides bug fixing and tuning, I know of several pieces of functionality yet to be added that are being worked on, including: * Web connectors (using a new connector protocol called mod_warp that is aware of webapp configuration settings, so you will not have to configure things twice). * JNDI context support (like that used in J2EE servers) for the and configuration parameters in the deployment descriptor. If you are interested in contributing to Tomcat 4.0, there is a "wish list" document in file "catalina/STATUS.html" in the jakarta-tomcat-4.0 source tree. Feel free to propose new ideas, or to volunteer to work on one of these. Craig McClanahan <=
RE: connector status in tomcat 4
>Ok, another question then. Please, >What is it that the connector has to be able to do? Is it >sufficient if it >simply can forward the HTTP request to tomcat or does it need >to play around >with it? I guess it must do something or the disscusion on ajp13/jk and >warp/webapp wouldn't be. The web-server connector forward request to tomcat and add some information, like the SESSION-COOKIES. In return the tomcat add a var, jvmroute, which is used in load-balancing config to be sure that the same tomcat will serve the next queries for that session. The connector use a simple protocol, ajp12/13/14, to forward the request. You may imagine a web-connector forwarding the request using HTTP protocol, but this one is more complex to handle. >// Erik > >> -Original Message- >> From: kevin seguin [mailto:[EMAIL PROTECTED]] >> Sent: Monday, May 28, 2001 5:47 PM >> To: [EMAIL PROTECTED] >> Subject: Re: connector status in tomcat 4 >> >> for example, in my case, currently all i care about is being able to >> forward requests based on uri from iis and netscape to >tomcat. so, for >> me, ajp does what i need it to, while warp/webapp currently >does not (no >> iis/netscape support yet). hence, i would pick ajp. >> >> now, i'm not saying one is better than the other. i'm just >saying that >> one might be better than the other in certain circumstances, >and now you >> have a choice. >> >
Re: connector status in tomcat 4
But I'm Win32 user ! - Original Message - From: "Pier P. Fumagalli" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 29, 2001 9:00 AM Subject: Re: connector status in tomcat 4 > egcs12md at [EMAIL PROTECTED] wrote: > > > Where to download ajp13/jk & ajp14/jk connectors for Apache Tomcat 4.0 ? > > Check out the jakarta-tomcat-connectors CVS module. > > Pier > >
Re: connector status in tomcat 4
egcs12md wrote: > > Where to download ajp13/jk & ajp14/jk connectors for Apache Tomcat 4.0 ? > you need to checkout the cvs module jakarta-tomcat-connectors and build from source. i don't think the build instructions are very detailed... the build.xml files will have to suffice for now. anyway, short version of instructions: cvs co jakarta-tomcat-connectors cd jakarta-tomcat-connectors/util ant cd ../jk ant i will be updating instructions, build.xml, etc. in the near future. -kevin. > - Original Message - > From: "kevin seguin" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, May 28, 2001 9:04 PM > Subject: Re: connector status in tomcat 4 > > > GOMEZ Henri wrote: > > > > > > >My question is what the status is on the apache connector in > > > >tomcat 4. I've > > > >been testing Jakarta 4 in standalone mode and is very pleased > > > >with it, but > > > >we can't run it like that once we release the system for all > > > >our students.. > > > >;) > > > > > > There is actually 2 connectors for Apache Tomcat 4.0 : > > > > > > - warp/webapp : Developped specifically for TC 4.0 have > > > autoconfig stuff but lack load-balancing or IIS/NES support > > > > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and > > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff > > > (will came in ajp14) but have load-balancing and IIS/NES > > > support. > > > > > > > er... the load-balancing doesn't work yet for tc 4 -- the java side of > > it hasn't been done yet. it shouldn't be too hard to do though :) i > > think it's just a matter of figuring out what to do with jvmRoute on the > > java side (set a cookie??). > > > > > Your contribution must match your need !) > >
Re: connector status in tomcat 4
egcs12md at [EMAIL PROTECTED] wrote: > Where to download ajp13/jk & ajp14/jk connectors for Apache Tomcat 4.0 ? Check out the jakarta-tomcat-connectors CVS module. Pier
Re: connector status in tomcat 4
Where to download ajp13/jk & ajp14/jk connectors for Apache Tomcat 4.0 ? - Original Message - From: "kevin seguin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 28, 2001 9:04 PM Subject: Re: connector status in tomcat 4 > GOMEZ Henri wrote: > > > > >My question is what the status is on the apache connector in > > >tomcat 4. I've > > >been testing Jakarta 4 in standalone mode and is very pleased > > >with it, but > > >we can't run it like that once we release the system for all > > >our students.. > > >;) > > > > There is actually 2 connectors for Apache Tomcat 4.0 : > > > > - warp/webapp : Developped specifically for TC 4.0 have > > autoconfig stuff but lack load-balancing or IIS/NES support > > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff > > (will came in ajp14) but have load-balancing and IIS/NES > > support. > > > > er... the load-balancing doesn't work yet for tc 4 -- the java side of > it hasn't been done yet. it shouldn't be too hard to do though :) i > think it's just a matter of figuring out what to do with jvmRoute on the > java side (set a cookie??). > > > Your contribution must match your need !) >
Re: connector status in tomcat 4
GOMEZ Henri at [EMAIL PROTECTED] wrote: >> In that case, what is the point of warp. Is it going to be >> faster, more scalable or something? > > warp is a whole new developpement using > very recent lib tools like APR. And a bunch of other features and improvements, but it seems that no one ever listen to what I write - technically speaking :) :) :) :) >> If not why was it created? > > That's a good question and who has the answer ? I do, and the mailing list archive... Check out for subjects like WARP :) Pier
Re: connector status in tomcat 4
Erik Hellman at [EMAIL PROTECTED] wrote: > Ok, another question then. > > What is it that the connector has to be able to do? Is it sufficient if it > simply can forward the HTTP request to tomcat or does it need to play around > with it? I guess it must do something or the disscusion on ajp13/jk and > warp/webapp wouldn't be. More or less... Yes, but it needs to do it in an efficient way, trying to be as thin as possible and so on... Long story (and it's 2 am of a bank holiday day right now :) Pier
Re: connector status in tomcat 4
Dave Oxley at [EMAIL PROTECTED] wrote: > In that case, what is the point of warp. Is it going to be faster, more > scalable or something? If not why was it created? It has a completely different architecture and approach to the problem of passing HTTP requests between two endpoints in remote servers... It tries not to be a hack, and that's all, but I'm not going over the same fight I'm dodging since months... Pier
Re: connector status in tomcat 4
Erik Hellman wrote: > > Ok, another question then. > > What is it that the connector has to be able to do? Is it sufficient if it > simply can forward the HTTP request to tomcat or does it need to play around > with it? I guess it must do something or the disscusion on ajp13/jk and > warp/webapp wouldn't be. i think in the simplest case, forwarding an HTTP request is enough. i think that some of the things warp/webapp might add are security (honoring security stuff specified in a webapp's web.xml), auto-config, etc.. again, i'm not that familiar with warp/webapp. ajp14 will have auto-config, too. > > // Erik > > > -Original Message- > > From: kevin seguin [mailto:[EMAIL PROTECTED]] > > Sent: Monday, May 28, 2001 5:47 PM > > To: [EMAIL PROTECTED] > > Subject: Re: connector status in tomcat 4 > > > > for example, in my case, currently all i care about is being able to > > forward requests based on uri from iis and netscape to tomcat. so, for > > me, ajp does what i need it to, while warp/webapp currently does not (no > > iis/netscape support yet). hence, i would pick ajp. > > > > now, i'm not saying one is better than the other. i'm just saying that > > one might be better than the other in certain circumstances, and now you > > have a choice. > >
RE: connector status in tomcat 4
Ok, another question then. What is it that the connector has to be able to do? Is it sufficient if it simply can forward the HTTP request to tomcat or does it need to play around with it? I guess it must do something or the disscusion on ajp13/jk and warp/webapp wouldn't be. // Erik > -Original Message- > From: kevin seguin [mailto:[EMAIL PROTECTED]] > Sent: Monday, May 28, 2001 5:47 PM > To: [EMAIL PROTECTED] > Subject: Re: connector status in tomcat 4 > > for example, in my case, currently all i care about is being able to > forward requests based on uri from iis and netscape to tomcat. so, for > me, ajp does what i need it to, while warp/webapp currently does not (no > iis/netscape support yet). hence, i would pick ajp. > > now, i'm not saying one is better than the other. i'm just saying that > one might be better than the other in certain circumstances, and now you > have a choice. >
RE: connector status in tomcat 4
>In that case, what is the point of warp. Is it going to be >faster, more scalable or something? warp is a whole new developpement using very recent lib tools like APR. >If not why was it created? That's a good question and who has the answer ? >Dave >[EMAIL PROTECTED] > > >>From: GOMEZ Henri <[EMAIL PROTECTED]> >>Reply-To: [EMAIL PROTECTED] >>To: [EMAIL PROTECTED] >>Subject: RE: connector status in tomcat 4 >>Date: Mon, 28 May 2001 17:43:41 +0200 >> >> >I thought the idea of warp/webapp was that it was to support >> >servlet api 2.3 >> >and ajp/jk couldn't eaily be modified to support the new specs. >> >>What's the supposed features in 2.3 that ajp/jk couldn't support ? >>At least there will be in ajp14/jk the autoconfig (ie list of >>URL/URI handled ) => >> >>/examples/servlet/* >>/examples/*.jsp >>/examples/*.xml >> >> > >> >Dave >> >[EMAIL PROTECTED] >> > >> > >> >>From: kevin seguin <[EMAIL PROTECTED]> >> >>Reply-To: [EMAIL PROTECTED] >> >>To: [EMAIL PROTECTED] >> >>Subject: Re: connector status in tomcat 4 >> >>Date: Mon, 28 May 2001 09:52:43 -0500 >> >> >> >> > >> >> > Ok, so which one would you say should has highest priority? >> >> > >> >> >> >>that probably depends on who you ask ;-) >> >> >> >> > Having a quick look at the CVS repository I see >> >>jakarta-tomcat-connectors, >> >> > which contains the jk-park, and in jakarta-tomcat I see >> >the warp/webapp. >> >>Is >> >> > this right? Won't ajp13/jk be included in tc4? Is it going to be >> >>replaced by >> >> > warp/webapp? >> >> > >> >> >> >>jakarta-tomcat-connectors (jtc) is a new module where >connectors like >> >>ajp, warp/webapp, etc. should live. the idea is that the >> >core parts of >> >>connectors should be container-agnostic. only the request/response >> >>adapters should know about containers. >> >> >> >>ajp/jk will not be "included" in tc4, but it will support >tc4 -- there >> >>will be (is) an ajp13 connector for tc 4 (it's is a work >in progress). >> >>going forward, ajp connectors for tc 3, tc 4, and maybe other >> >containers >> >>will live in jtc. >> >> >> >>warp/webapp will not replace ajp/jk, but it will give you another >> >>choice. you'll be free to make the decision yourself as to what >> >>connector you want to use. >> >> >> >> > // Erik >> >> > >> >> > > -Original Message- >> >> > > From: kevin seguin [mailto:[EMAIL PROTECTED]] >> >> > > Sent: Monday, May 28, 2001 3:05 PM >> >> > > To: [EMAIL PROTECTED] >> >> > > Subject: Re: connector status in tomcat 4 >> >> > > >> >> > > >> >> > > GOMEZ Henri wrote: >> >> > > > >> >> > > > >My question is what the status is on the apache >connector in >> >> > > > >tomcat 4. I've >> >> > > > >been testing Jakarta 4 in standalone mode and is >very pleased >> >> > > > >with it, but >> >> > > > >we can't run it like that once we release the >system for all >> >> > > > >our students.. >> >> > > > >;) >> >> > > > >> >> > > > There is actually 2 connectors for Apache Tomcat 4.0 : >> >> > > > >> >> > > > - warp/webapp : Developped specifically for TC 4.0 have >> >> > > > autoconfig stuff but lack load-balancing or >IIS/NES support >> >> > > > >> >> > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and >> >> > > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff >> >> > > > (will came in ajp14) but have load-balancing and IIS/NES >> >> > > > support. >> >> > > > >> >> > > >> >> > > er... the load-balancing doesn't work yet for tc 4 -- >> >the java side >> >>of >> >> > > it hasn't been done yet. it shouldn't be too hard to do >> >though :) i >> >> > > think it's just a matter of figuring out what to do with >> >jvmRoute on >> >>the >> >> > > java side (set a cookie??). >> >> > > >> >> > > > Your contribution must match your need !) >> > >> >___ >> >__ >> >Get Your Private, Free E-mail from MSN Hotmail at >>http://www.hotmail.com. > >___ >__ >Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Re: connector status in tomcat 4
Dave Oxley wrote: > > I thought the idea of warp/webapp was that it was to support servlet api 2.3 > and ajp/jk couldn't eaily be modified to support the new specs. > i don't know all of the details of warp/webapp. my main point was, both ajp and warp/webapp will be usable with tc 4. as a user, you are free to look at the features of both, and based on your own requirements, pick which is best for you. for example, in my case, currently all i care about is being able to forward requests based on uri from iis and netscape to tomcat. so, for me, ajp does what i need it to, while warp/webapp currently does not (no iis/netscape support yet). hence, i would pick ajp. now, i'm not saying one is better than the other. i'm just saying that one might be better than the other in certain circumstances, and now you have a choice. > Dave > [EMAIL PROTECTED] > > >From: kevin seguin <[EMAIL PROTECTED]> > >Reply-To: [EMAIL PROTECTED] > >To: [EMAIL PROTECTED] > >Subject: Re: connector status in tomcat 4 > >Date: Mon, 28 May 2001 09:52:43 -0500 > > > > > > > > Ok, so which one would you say should has highest priority? > > > > > > >that probably depends on who you ask ;-) > > > > > Having a quick look at the CVS repository I see > >jakarta-tomcat-connectors, > > > which contains the jk-park, and in jakarta-tomcat I see the warp/webapp. > >Is > > > this right? Won't ajp13/jk be included in tc4? Is it going to be > >replaced by > > > warp/webapp? > > > > > > >jakarta-tomcat-connectors (jtc) is a new module where connectors like > >ajp, warp/webapp, etc. should live. the idea is that the core parts of > >connectors should be container-agnostic. only the request/response > >adapters should know about containers. > > > >ajp/jk will not be "included" in tc4, but it will support tc4 -- there > >will be (is) an ajp13 connector for tc 4 (it's is a work in progress). > >going forward, ajp connectors for tc 3, tc 4, and maybe other containers > >will live in jtc. > > > >warp/webapp will not replace ajp/jk, but it will give you another > >choice. you'll be free to make the decision yourself as to what > >connector you want to use. > > > > > // Erik > > > > > > > -Original Message- > > > > From: kevin seguin [mailto:[EMAIL PROTECTED]] > > > > Sent: Monday, May 28, 2001 3:05 PM > > > > To: [EMAIL PROTECTED] > > > > Subject: Re: connector status in tomcat 4 > > > > > > > > > > > > GOMEZ Henri wrote: > > > > > > > > > > >My question is what the status is on the apache connector in > > > > > >tomcat 4. I've > > > > > >been testing Jakarta 4 in standalone mode and is very pleased > > > > > >with it, but > > > > > >we can't run it like that once we release the system for all > > > > > >our students.. > > > > > >;) > > > > > > > > > > There is actually 2 connectors for Apache Tomcat 4.0 : > > > > > > > > > > - warp/webapp : Developped specifically for TC 4.0 have > > > > > autoconfig stuff but lack load-balancing or IIS/NES support > > > > > > > > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and > > > > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff > > > > > (will came in ajp14) but have load-balancing and IIS/NES > > > > > support. > > > > > > > > > > > > > er... the load-balancing doesn't work yet for tc 4 -- the java side > >of > > > > it hasn't been done yet. it shouldn't be too hard to do though :) i > > > > think it's just a matter of figuring out what to do with jvmRoute on > >the > > > > java side (set a cookie??). > > > > > > > > > Your contribution must match your need !) > > _ > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
RE: connector status in tomcat 4
In that case, what is the point of warp. Is it going to be faster, more scalable or something? If not why was it created? Dave [EMAIL PROTECTED] >From: GOMEZ Henri <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: RE: connector status in tomcat 4 >Date: Mon, 28 May 2001 17:43:41 +0200 > > >I thought the idea of warp/webapp was that it was to support > >servlet api 2.3 > >and ajp/jk couldn't eaily be modified to support the new specs. > >What's the supposed features in 2.3 that ajp/jk couldn't support ? >At least there will be in ajp14/jk the autoconfig (ie list of >URL/URI handled ) => > >/examples/servlet/* >/examples/*.jsp >/examples/*.xml > > > > >Dave > >[EMAIL PROTECTED] > > > > > >>From: kevin seguin <[EMAIL PROTECTED]> > >>Reply-To: [EMAIL PROTECTED] > >>To: [EMAIL PROTECTED] > >>Subject: Re: connector status in tomcat 4 > >>Date: Mon, 28 May 2001 09:52:43 -0500 > >> > >> > > >> > Ok, so which one would you say should has highest priority? > >> > > >> > >>that probably depends on who you ask ;-) > >> > >> > Having a quick look at the CVS repository I see > >>jakarta-tomcat-connectors, > >> > which contains the jk-park, and in jakarta-tomcat I see > >the warp/webapp. > >>Is > >> > this right? Won't ajp13/jk be included in tc4? Is it going to be > >>replaced by > >> > warp/webapp? > >> > > >> > >>jakarta-tomcat-connectors (jtc) is a new module where connectors like > >>ajp, warp/webapp, etc. should live. the idea is that the > >core parts of > >>connectors should be container-agnostic. only the request/response > >>adapters should know about containers. > >> > >>ajp/jk will not be "included" in tc4, but it will support tc4 -- there > >>will be (is) an ajp13 connector for tc 4 (it's is a work in progress). > >>going forward, ajp connectors for tc 3, tc 4, and maybe other > >containers > >>will live in jtc. > >> > >>warp/webapp will not replace ajp/jk, but it will give you another > >>choice. you'll be free to make the decision yourself as to what > >>connector you want to use. > >> > >> > // Erik > >> > > >> > > -Original Message- > >> > > From: kevin seguin [mailto:[EMAIL PROTECTED]] > >> > > Sent: Monday, May 28, 2001 3:05 PM > >> > > To: [EMAIL PROTECTED] > >> > > Subject: Re: connector status in tomcat 4 > >> > > > >> > > > >> > > GOMEZ Henri wrote: > >> > > > > >> > > > >My question is what the status is on the apache connector in > >> > > > >tomcat 4. I've > >> > > > >been testing Jakarta 4 in standalone mode and is very pleased > >> > > > >with it, but > >> > > > >we can't run it like that once we release the system for all > >> > > > >our students.. > >> > > > >;) > >> > > > > >> > > > There is actually 2 connectors for Apache Tomcat 4.0 : > >> > > > > >> > > > - warp/webapp : Developped specifically for TC 4.0 have > >> > > > autoconfig stuff but lack load-balancing or IIS/NES support > >> > > > > >> > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and > >> > > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff > >> > > > (will came in ajp14) but have load-balancing and IIS/NES > >> > > > support. > >> > > > > >> > > > >> > > er... the load-balancing doesn't work yet for tc 4 -- > >the java side > >>of > >> > > it hasn't been done yet. it shouldn't be too hard to do > >though :) i > >> > > think it's just a matter of figuring out what to do with > >jvmRoute on > >>the > >> > > java side (set a cookie??). > >> > > > >> > > > Your contribution must match your need !) > > > >___ > >__ > >Get Your Private, Free E-mail from MSN Hotmail at >http://www.hotmail.com. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
RE: connector status in tomcat 4
>I thought the idea of warp/webapp was that it was to support >servlet api 2.3 >and ajp/jk couldn't eaily be modified to support the new specs. What's the supposed features in 2.3 that ajp/jk couldn't support ? At least there will be in ajp14/jk the autoconfig (ie list of URL/URI handled ) => /examples/servlet/* /examples/*.jsp /examples/*.xml > >Dave >[EMAIL PROTECTED] > > >>From: kevin seguin <[EMAIL PROTECTED]> >>Reply-To: [EMAIL PROTECTED] >>To: [EMAIL PROTECTED] >>Subject: Re: connector status in tomcat 4 >>Date: Mon, 28 May 2001 09:52:43 -0500 >> >> > >> > Ok, so which one would you say should has highest priority? >> > >> >>that probably depends on who you ask ;-) >> >> > Having a quick look at the CVS repository I see >>jakarta-tomcat-connectors, >> > which contains the jk-park, and in jakarta-tomcat I see >the warp/webapp. >>Is >> > this right? Won't ajp13/jk be included in tc4? Is it going to be >>replaced by >> > warp/webapp? >> > >> >>jakarta-tomcat-connectors (jtc) is a new module where connectors like >>ajp, warp/webapp, etc. should live. the idea is that the >core parts of >>connectors should be container-agnostic. only the request/response >>adapters should know about containers. >> >>ajp/jk will not be "included" in tc4, but it will support tc4 -- there >>will be (is) an ajp13 connector for tc 4 (it's is a work in progress). >>going forward, ajp connectors for tc 3, tc 4, and maybe other >containers >>will live in jtc. >> >>warp/webapp will not replace ajp/jk, but it will give you another >>choice. you'll be free to make the decision yourself as to what >>connector you want to use. >> >> > // Erik >> > >> > > -Original Message- >> > > From: kevin seguin [mailto:[EMAIL PROTECTED]] >> > > Sent: Monday, May 28, 2001 3:05 PM >> > > To: [EMAIL PROTECTED] >> > > Subject: Re: connector status in tomcat 4 >> > > >> > > >> > > GOMEZ Henri wrote: >> > > > >> > > > >My question is what the status is on the apache connector in >> > > > >tomcat 4. I've >> > > > >been testing Jakarta 4 in standalone mode and is very pleased >> > > > >with it, but >> > > > >we can't run it like that once we release the system for all >> > > > >our students.. >> > > > >;) >> > > > >> > > > There is actually 2 connectors for Apache Tomcat 4.0 : >> > > > >> > > > - warp/webapp : Developped specifically for TC 4.0 have >> > > > autoconfig stuff but lack load-balancing or IIS/NES support >> > > > >> > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and >> > > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff >> > > > (will came in ajp14) but have load-balancing and IIS/NES >> > > > support. >> > > > >> > > >> > > er... the load-balancing doesn't work yet for tc 4 -- >the java side >>of >> > > it hasn't been done yet. it shouldn't be too hard to do >though :) i >> > > think it's just a matter of figuring out what to do with >jvmRoute on >>the >> > > java side (set a cookie??). >> > > >> > > > Your contribution must match your need !) > >___ >__ >Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Re: connector status in tomcat 4
I thought the idea of warp/webapp was that it was to support servlet api 2.3 and ajp/jk couldn't eaily be modified to support the new specs. Dave [EMAIL PROTECTED] >From: kevin seguin <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: Re: connector status in tomcat 4 >Date: Mon, 28 May 2001 09:52:43 -0500 > > > > > Ok, so which one would you say should has highest priority? > > > >that probably depends on who you ask ;-) > > > Having a quick look at the CVS repository I see >jakarta-tomcat-connectors, > > which contains the jk-park, and in jakarta-tomcat I see the warp/webapp. >Is > > this right? Won't ajp13/jk be included in tc4? Is it going to be >replaced by > > warp/webapp? > > > >jakarta-tomcat-connectors (jtc) is a new module where connectors like >ajp, warp/webapp, etc. should live. the idea is that the core parts of >connectors should be container-agnostic. only the request/response >adapters should know about containers. > >ajp/jk will not be "included" in tc4, but it will support tc4 -- there >will be (is) an ajp13 connector for tc 4 (it's is a work in progress). >going forward, ajp connectors for tc 3, tc 4, and maybe other containers >will live in jtc. > >warp/webapp will not replace ajp/jk, but it will give you another >choice. you'll be free to make the decision yourself as to what >connector you want to use. > > > // Erik > > > > > -Original Message- > > > From: kevin seguin [mailto:[EMAIL PROTECTED]] > > > Sent: Monday, May 28, 2001 3:05 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: connector status in tomcat 4 > > > > > > > > > GOMEZ Henri wrote: > > > > > > > > >My question is what the status is on the apache connector in > > > > >tomcat 4. I've > > > > >been testing Jakarta 4 in standalone mode and is very pleased > > > > >with it, but > > > > >we can't run it like that once we release the system for all > > > > >our students.. > > > > >;) > > > > > > > > There is actually 2 connectors for Apache Tomcat 4.0 : > > > > > > > > - warp/webapp : Developped specifically for TC 4.0 have > > > > autoconfig stuff but lack load-balancing or IIS/NES support > > > > > > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and > > > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff > > > > (will came in ajp14) but have load-balancing and IIS/NES > > > > support. > > > > > > > > > > er... the load-balancing doesn't work yet for tc 4 -- the java side >of > > > it hasn't been done yet. it shouldn't be too hard to do though :) i > > > think it's just a matter of figuring out what to do with jvmRoute on >the > > > java side (set a cookie??). > > > > > > > Your contribution must match your need !) _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Re: connector status in tomcat 4
> > Ok, so which one would you say should has highest priority? > that probably depends on who you ask ;-) > Having a quick look at the CVS repository I see jakarta-tomcat-connectors, > which contains the jk-park, and in jakarta-tomcat I see the warp/webapp. Is > this right? Won't ajp13/jk be included in tc4? Is it going to be replaced by > warp/webapp? > jakarta-tomcat-connectors (jtc) is a new module where connectors like ajp, warp/webapp, etc. should live. the idea is that the core parts of connectors should be container-agnostic. only the request/response adapters should know about containers. ajp/jk will not be "included" in tc4, but it will support tc4 -- there will be (is) an ajp13 connector for tc 4 (it's is a work in progress). going forward, ajp connectors for tc 3, tc 4, and maybe other containers will live in jtc. warp/webapp will not replace ajp/jk, but it will give you another choice. you'll be free to make the decision yourself as to what connector you want to use. > // Erik > > > -Original Message- > > From: kevin seguin [mailto:[EMAIL PROTECTED]] > > Sent: Monday, May 28, 2001 3:05 PM > > To: [EMAIL PROTECTED] > > Subject: Re: connector status in tomcat 4 > > > > > > GOMEZ Henri wrote: > > > > > > >My question is what the status is on the apache connector in > > > >tomcat 4. I've > > > >been testing Jakarta 4 in standalone mode and is very pleased > > > >with it, but > > > >we can't run it like that once we release the system for all > > > >our students.. > > > >;) > > > > > > There is actually 2 connectors for Apache Tomcat 4.0 : > > > > > > - warp/webapp : Developped specifically for TC 4.0 have > > > autoconfig stuff but lack load-balancing or IIS/NES support > > > > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and > > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff > > > (will came in ajp14) but have load-balancing and IIS/NES > > > support. > > > > > > > er... the load-balancing doesn't work yet for tc 4 -- the java side of > > it hasn't been done yet. it shouldn't be too hard to do though :) i > > think it's just a matter of figuring out what to do with jvmRoute on the > > java side (set a cookie??). > > > > > Your contribution must match your need !)
RE: connector status in tomcat 4
Ok, so which one would you say should has highest priority? Having a quick look at the CVS repository I see jakarta-tomcat-connectors, which contains the jk-park, and in jakarta-tomcat I see the warp/webapp. Is this right? Won't ajp13/jk be included in tc4? Is it going to be replaced by warp/webapp? // Erik > -Original Message- > From: kevin seguin [mailto:[EMAIL PROTECTED]] > Sent: Monday, May 28, 2001 3:05 PM > To: [EMAIL PROTECTED] > Subject: Re: connector status in tomcat 4 > > > GOMEZ Henri wrote: > > > > >My question is what the status is on the apache connector in > > >tomcat 4. I've > > >been testing Jakarta 4 in standalone mode and is very pleased > > >with it, but > > >we can't run it like that once we release the system for all > > >our students.. > > >;) > > > > There is actually 2 connectors for Apache Tomcat 4.0 : > > > > - warp/webapp : Developped specifically for TC 4.0 have > > autoconfig stuff but lack load-balancing or IIS/NES support > > > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and > > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff > > (will came in ajp14) but have load-balancing and IIS/NES > > support. > > > > er... the load-balancing doesn't work yet for tc 4 -- the java side of > it hasn't been done yet. it shouldn't be too hard to do though :) i > think it's just a matter of figuring out what to do with jvmRoute on the > java side (set a cookie??). > > > Your contribution must match your need !)
Re: connector status in tomcat 4
GOMEZ Henri wrote: > > >My question is what the status is on the apache connector in > >tomcat 4. I've > >been testing Jakarta 4 in standalone mode and is very pleased > >with it, but > >we can't run it like that once we release the system for all > >our students.. > >;) > > There is actually 2 connectors for Apache Tomcat 4.0 : > > - warp/webapp : Developped specifically for TC 4.0 have > autoconfig stuff but lack load-balancing or IIS/NES support > > - ajp13/jk : Available since TC 3.2, works with TC 3.3 and > now with 4.0 (thanks to Kevin). Miss the autoconfig stuff > (will came in ajp14) but have load-balancing and IIS/NES > support. > er... the load-balancing doesn't work yet for tc 4 -- the java side of it hasn't been done yet. it shouldn't be too hard to do though :) i think it's just a matter of figuring out what to do with jvmRoute on the java side (set a cookie??). > Your contribution must match your need !)
RE: connector status in tomcat 4
>My question is what the status is on the apache connector in >tomcat 4. I've >been testing Jakarta 4 in standalone mode and is very pleased >with it, but >we can't run it like that once we release the system for all >our students.. >;) There is actually 2 connectors for Apache Tomcat 4.0 : - warp/webapp : Developped specifically for TC 4.0 have autoconfig stuff but lack load-balancing or IIS/NES support - ajp13/jk : Available since TC 3.2, works with TC 3.3 and now with 4.0 (thanks to Kevin). Miss the autoconfig stuff (will came in ajp14) but have load-balancing and IIS/NES support. Your contribution must match your need !)
Re: connector status in tomcat 4
which connector are you talking about? the new warp/webapp stuff, or the ajp connector(s)? i don't know much about warp/webapp, but i do know the ajp13 connector for tomcat 4 is a work in progress. it's kind of in a holding pattern right now, waiting for some other things to happen. hopefully, at least by the end of the summer, the ajp13 (maybe even ajp14) connector for tomcat 4 will be in pretty good shape. -kevin. Erik Hellman wrote: > > This summer I will be involved in a quite large project at our University > aiming to create a web-based system for administrating and presenting > course-information (and some other nifty features..). We will be using > tomcat 4 for this and apache as the webserver. The final product will be > released during the next semester (september-october). > > My question is what the status is on the apache connector in tomcat 4. I've > been testing Jakarta 4 in standalone mode and is very pleased with it, but > we can't run it like that once we release the system for all our students.. > ;) > > Is the state of the connector good enough to start using or does it still > need alot of development? In that case I would be interrested in joining the > development on that part of tomcat. Who should I contact in this case? > > Another thing I was wondering; is if there is any date planned for the > release of tomcat 4.0? I searched the archive, but didn't find anything > mentioning that. You've probably seen this question hundreds of times, or > I've missed something when searching.. :) > > regards > Erik Hellman
Re: connector status in tomcat 4
Erik Hellman at [EMAIL PROTECTED] wrote: > This summer I will be involved in a quite large project at our University > aiming to create a web-based system for administrating and presenting > course-information (and some other nifty features..). We will be using > tomcat 4 for this and apache as the webserver. The final product will be > released during the next semester (september-october). > > My question is what the status is on the apache connector in tomcat 4. I've > been testing Jakarta 4 in standalone mode and is very pleased with it, but > we can't run it like that once we release the system for all our students.. > ;) > > Is the state of the connector good enough to start using or does it still > need alot of development? In that case I would be interrested in joining the > development on that part of tomcat. Who should I contact in this case? > > Another thing I was wondering; is if there is any date planned for the > release of tomcat 4.0? I searched the archive, but didn't find anything > mentioning that. You've probably seen this question hundreds of times, or > I've missed something when searching.. :) Pleased to hear that we have some volunteers :) :) (That's great indeed). The first thing to do, is check it out of the CVS and see if it compiles on your system, there is a readme file that details what you need... Please do it, and tell me how far you got (it's a good startpoint, indeed :) Pier
