Re: J2SE 5

Hi,

New prototype thread manager could be written, but once benchmarked, they might need tuning that
concurrent.util may deny. FiniteQueue is a good example of fine tuned queue, since the queue
elements wrappers (ssLinkedList) are pooled. Just proove it to yourself: ssLinkedList is MUCH
faster than any jdk list. Matt did a very good job. Not perfect, but very good.

In my opinion, this concurrent util stuff is just making the whole concurrent programming learning
curve more difficult to beginners and even intermediate level programmers.

There is only 3 construct in java for thread programming: 'synchronized', 'wait' and
'notify[all]'.

If anybody lack imagination to solve a problem with such simple yet complete functionnality,
that's because they haven't had a course on concurrent programming first. So, how would you expect
such guy to understand and 'trust' about 50 classes behaviors if they don't get the patterns
first?

I've seen sandstorm runtime to the molecule level: frankly, although some j2se 5 classes sound
pretty close, it would just make this seda implementation less efficient. Any already fine-tuned
thread manager wouldn't benefit from it.

Have fun.



--- Jean Morissette <[email protected]> wrote:
> Now that J2SE 5 is officially out, are there any plans to replace some 
> data structures or interfaces by java.util.concurrent api?



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl