jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol" <vmas...@octo.com>
Subject RE: WebRequest and header values
Date Sat, 22 Feb 2003 11:27:39 GMT
Hi Jason,

+1 for both! Waiting for the patches ... :-)


> -----Original Message-----
> From: Robertson, Jason [mailto:Jason.Robertson@acs-inc.com]
> Sent: 11 February 2003 03:26
> To: 'Cactus Users List'
> Subject: WebRequest and header values
> The current WebRequest object only has an "addHeader" method, and
> come
> across a need for a "setHeader" method and I was wondering if there
> any
> specific reason something like this isn't there. The difference would
> that in setHeader it would replace any existing values with the new
> The issue has appeared because some of my team members implemented a
> case that in 29 of the 34 test methods has a common configuration that
> they
> put into the begin() method. Then, in those 5 other tests, they need
> different configuration options which they put into beginXXX() methods
> (this
> way they didn't have to write 34 beginXXX() methods). However, the
> configuration involves setting header values and since there's no way
> override the existing headers the begin() configuration put there they
> can't
> be replaced in beginXXX().
> Also, it was suggested that instead of using a Vector for the header
> values
> it should be an ArrayList (or some other unsynchronized collection) so
> that
> you don't pay the slight but unnecessary synchronization penalty.
> I have the guy rewriting WebRequest with these changes, I'll submit it
> when
> he has it ready. I just wanted to toss these comments out before he
> too
> far.
> Jason
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org

View raw message