John McNally wrote:
> I know it is a pain for those developing applications while trying to
> keep up with the latest code changes in Turbine. We started using the
> Vector back when the other Collections were not available. The reasons
> to update the code are that it is better to code to interfaces and the
> Vector is inefficient compared to, for example, the ArrayList which is a
> better choice in many circumstances including the Peers.
+1 to the change. Collections framework is way better than the old
Vector/Enumeration classes.
> The reason to do it now rather than later is to minimize the number of
> people that it affects and to minimize the impact on the people that it
> does affect because as you say it will affect a lot of your code now, I
> am sure it will affect more later.
I'm expecting to hear some loud whining from my coworkers when the next
turbine.jar hits our CVS. A quick "find -name \*Peer.java" revealed 71
Peer classes in our project. A whole bunch of code will need fixing.
When you live on the bleeding edge, expect to bleed a little...
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
