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.
Difference between revisions of "EclipseLink/Design Philosophy"
m (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...) |
m |
||
| Line 1: | Line 1: | ||
| − | =Design Philosophy= | + | <!--=Design Philosophy= |
*This page is a repository for all things that aide in the design process...some of this is likely internally oriented. | *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== | ==Questions to be answered by Developers and Managers for Developers== | ||
| Line 5: | Line 5: | ||
*What is the thing or ordered list of things that we absolutely must keep optimized when developing for EclipseLink? | *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. | **One word would be nice. Lets start with time/space/concurrency or memory/speed/locking. We need a order or development for these three. | ||
| + | --> | ||