Eclipse Community Forums: EclipseLink » Why are you not using java.util.concurrent classes?

Home » Eclipse Projects » EclipseLink » Why are you not using java.util.concurrent classes?(Support for concurrent programming usage patterns.)

Show: Today's Messages :: Show Polls :: Message Navigator

Why are you not using java.util.concurrent classes? [message #1174954]

Thu, 07 November 2013 07:25

Marvin Toll
Messages: 30
Registered: July 2009

Member

As I review more of your code base over time, it appears that there is a pattern to not take advantage of advances to the Java language.

This pattern is strikingly apparent with a lack of java.util.concurrent classes.

I remember the Toplink days, back in 2005, scratching my head trying to figure out why you were still using Vectors.

What is being put at risk is not simply performance and scalability... but reliability in the context of contemporary multicore (concurrent) coding practices. Said more directly, in my opinion, you are marginalizing your product by not supporting concurrent programming usage patterns.

Marvin Toll
CTO, Pattern Enabled Development
http://PatternEnabled.com

[Updated on: Thu, 07 November 2013 07:27]

Report message to a moderator

Previous Topic:	Retrieve object and dependencies with only one SQL request
Next Topic:	Issue with new entities after delete then merge

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Mar 08 02:18:44 EST 2014