Why is Vector used prolifically?  Is this just an anachronism?
 
Vector has synchronized methods, which are slow, and as a concrete
implementation class it doesn't offer a whole lot of flexibility for
novel implementation strategies (like backing a List with a ResultSet
directly).
 
Is it just a question of spending the time to do a search/replace on the
code?  If so, I'll be happy to volunteer.    I notice that there are
several Java2 collections in the code already, so nobody is trying to
keep compatibility with JDK 1.1.  Since 3.0 is a major release, it seems
like this would be the best time to make any major interface changes.
 
Jeff Schnitzer
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
 


Reply via email to