I know, I've been using them increasingly more the last six months or so.
The question is more whether or not we should replace all Vectors within
Turbine with ArrayLists or should we identify a number (of vectors) that
have to remain (vectors) and make the rest ArrayLists???
/colin
----- Original Message -----
From: "Gareth Coltman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 24, 2001 7:02 PM
Subject: RE: Vectors vs ArrayList
> > Does this mean that we should/will replace *all* vectors with
> > ArrayLists or
> > only specific ones? Will this not break some code?
> >
>
> ArrayList implements all Vector's functionality, it just isn't thread
safe.
> If you use it you have to synchronize manually.
>
> >
> >
> > > on 5/24/01 1:25 AM, "Gareth Coltman" <[EMAIL PROTECTED]>
> > wrote:
> > >
> > > > Guys,
> > > >
> > > > I was reading this report by sun about jdk1.2 and it had some
> > benchmarks
> > > > showing that ArrayLists perform significantly better than Vectors
> > because
> > > > the treadsafe code overhead isn't there. Is there a reason why you
> > haven't
> > > > used ArrayLists in classes where there are no threading issues such
as
> > > > peers? Is it worth the change?
> > > >
> > > > Gareth
> > >
> > > Wow, that sounds like a great way that you can contribute to the
Turbine
> > > project! :-)
> > >
>
> -> Replace In Files
> ---->What: Vector
> ---->With: ArrayList
>
> Voila! My contribution to the Turbine project!
>
> :P
>
> Gareth
>
>
> ---------------------------------------------------------------------
> 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]
