Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Design Philosophy
< EclipseLink
Revision as of 19:40, 21 July 2010 by Unnamed Poltroon (Talk) (New page: =Design Philosophy= *This page is a repository for all things that aide in the design process...some of this is likely internally oriented. ==Questions to be answered by Developers and Man...)
Design Philosophy
- This page is a repository for all things that aide in the design process...some of this is likely internally oriented.
Questions to be answered by Developers and Managers for Developers
Q1: What is the number one optimization we need to keep in mind for all code changes?
- What is the thing or ordered list of things that we absolutely must keep optimized when developing for EclipseLink?
- One word would be nice. Lets start with time/space/concurrency or memory/speed/locking. We need a order or development for these three.