Re: Tomcat configuration tuning

[Charles N. Harvey III]

I've never actually used a profiler before.  I keep meaning to I swear.
Its my next big venture.  I just figured out unit testing about 2 weeks ago.
We just never have time for that silly testing and profiling stuff at my
company.  I never actually wrote the filter either.  But I have one around
that I could use to at least do some testing.
I'll try this "profiling" and try to get the results back to the list.

Charlie

Shapira, Yoav wrote:

Hi,
Did you profile the filter versus aspects?  Now that's a benchmark I'd
be really interested in.
To the original poster: assuming your filter is smart enough to check
the session for a "user is authenticated already" token, the /* mapping
is not that big a deal.  If you're re-authenticating every time, that's
terrible, and you should make your filter smarter.
Yoav Shapira
Millennium Research Informatics
 

-----Original Message-----
From: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 08, 2004 3:38 PM
To: Tomcat Users List
Subject: Re: Tomcat configuration tuning
I do just what you described below.  If the loginContext isn't in the
session,
I show do a global-forward to the login form.  And, because I didn't
   

want
 

to
have to put a session check into every Struts action I used AspectJ to
weave
in a pointcut into every action.  Works great.  I was considering going
with
a filter servlet instead but if you say its slow then maybe I did the
   

right
 

thing.

Charlie



Allistair Crossley wrote:

   

Slightly off-forum but related to my performance tuning of my tomcat
     

webapp, I am using the JCIFS NTLM authentication servlet as a filter.
   

The
 

filter is mapped to all requests /*. I just thought to myself on the
   

train
 

home whether because NTLM is a 3-way handshake, that this may be
   

causing
 

some kind of performance hit.
   

The filter authenticates the desktop user and then populates the
     

request.getRemoteUser. I suppose I "could" do this once with a login
servlet and then populate a session user object and if that ever
   

expires
 

redirect back to the login servlet.
   

Does anyone have an opinion on whether it would be worth my time
     

removing
 

the filter per request in favour of a once-only login action.
   

I appreciate this is off-tomcat, so no hard feelings if noone replies
     

;)
 

ADC

<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE>
-------------------------------------------------------
QAS Ltd.
Developers of QuickAddress Software
<a href="http://www.qas.com";>www.qas.com</a>
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT>


----------------------------------------------------------------------
     

--
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
     

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   





This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged.  This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender.  Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]