Thanks for the reply Tim, but I don't think my question was clear enough. Both the RequestBase and HttpRequestBase classes have their own isSecure instance variable and have their own setSecure() and isSecure() methods. The code in both classes seems to do the same thing. My question is, is there any reason why the methods and instance variable are duplicated in the HttpRequestBase class. It seems that the code in HttpRequestBase relating to the "secure" instance variable is not needed, as it is provided in its superclass, RequestBase.
Thanks, John ----- Original Message ----- From: "Tim Funk" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Sunday, January 26, 2003 2:28 AM Subject: Re: Question about duplication of secure property in RequestBase and HttpRequestBase > org.apache.catalina.connector.RequestBase implements ServletRequest. > http://jakarta.apache.org/tomcat/tomcat-4.0-doc/catalina/docs/api/org/apache /catalina/connector/RequestBase.html > > And isSecure is part of the interface of ServletRequest. > http://java.sun.com/products/servlet/2.3/javadoc/javax/servlet/ServletReques t.html#isSecure() > > -Tim > > John Sisson wrote: > > Hi, > > > > I noticed that both org.apache.catalina.connector.RequestBase and org.apache.catalina.connector.HttpRequestBase both have a "secure" instance variable and the setSecure(bool) isSecure() methods. Does anybody know the reason for this? > > > > Thanks, > > > > John > > > > > -- > 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]>
