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.
> >
