Standards are a Good Thing(TM) There is always a trade off between flexibility and having a rigid standard. In the long run keeping to a standard is usually the best policy.
I'm sure you understand how difficult it is to build flexibility to cover any situation - as shown by the inflexibility of your legacy systems ;-) ----- Original Message ----- From: "Firestar" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 18, 2001 12:52 PM Subject: RE: How to change session key name > But JRun does allow me to change it:) I was hoping > Tomcat 4.0 would be as flexible... > > For e.g. another gd thing abt JRun is that it allows > us to place our servlets and classes anywhere, instead > of WEB-INF folder. Specification or not, there are > times where due to certain reasons or legacy issues > internally, we have to break the 'rule'. And so far we > still can't move to Tomcat, as much as we would like > to...:( > > Firestar > > --- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > > > > > > On Thu, 18 Oct 2001, Jovie Castaneda wrote: > > > > > Date: Thu, 18 Oct 2001 09:28:46 +1000 > > > From: Jovie Castaneda <[EMAIL PROTECTED]> > > > Reply-To: [EMAIL PROTECTED] > > > To: [EMAIL PROTECTED] > > > Subject: RE: How to change session key name > > > > > > Hi Larry, > > > > > > Thanks for the reply I really want to make it > > but it seems that I cant > > > get > > > what's going on here is it beacause im using > > Tomcat 3.1? > > > > > > > The use of JSESSIONID for the cookie name is > > required by the servlet > > specification. Therefore it is not a configurable > > option. > > > > Craig > > > > > __________________________________________________ > Do You Yahoo!? > Make a great connection at Yahoo! Personals. > http://personals.yahoo.com >
