Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Q for the authors Craig and David

 
chris coleman
Ranch Hand
Posts: 42
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Craig and David..
First, congratulations on your new book, I hear it is simply fantastic.
This question came to mind, and it would be great of you to answer it when you're ready.
When you look forward to a time two years from now.. when JDO will have matured to 3.0 or 4.0 and picked up more useful features along the way... and you look at where you see JDO fitting into the landscape of java data layer technologies.. how would you describe that view you see ?
[ June 17, 2003: Message edited by: chris coleman ]
 
David Jordan
Author
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Fantastic? that is great to hear...
In two years, I suspect JDO 2.0 will be out and implementations will be supporting JDO 2.0. I bet we will be in the process of working on JDO 3.0. JDO 2.0 should standardize the OR mapping metadata across relational JDO implementations and it should add a lot more query capabilities.
I'll have to think some about JDO 3.0 features, which is very hard to guess at this point. I would guess that we would be providing more facilities to allow easy integration with other Java technologies used in architectures, whatever they may be at that point. Another open question is when new Java features will get released, like generics and metadata, which will definitely influence JDO's interface once they are released. For example, today you need to specify the element types of collections in the JDO metadata. That won't be necessary when generics come out. And metadata support should also further simplify the JDO interface.
 
Mike Farnham
Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If ADO.NET is Microsoft's abstraction of the PersistenceInterface, and JDO is the Java abstraction, could JDO 3.0 or 4.0 conceivably create an abstraction, at such a level that C# and Java might work with seamlessly against different datastores?
Talk about SilverBullets...
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic