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/SpecialProjects"
m (New page: =EclipseLink Special Projects Group= *<div style="border: 3px red solid;" align="center" ><font color="red">DISCLAIMER: This page reflects investigation into how EclipseLink technology can...) |
m |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | =EclipseLink Special Projects Group= | + | <!--=EclipseLink Special Projects Group= |
*<div style="border: 3px red solid;" align="center" ><font color="red">DISCLAIMER: This page reflects investigation into how EclipseLink technology can used as part of - or benefit from integration with other projects. It does NOT imply any formal certification from EclipseLink on these technologies or make any assumptions on the direction of the API. This page is purely experimental speculation.</font></div> | *<div style="border: 3px red solid;" align="center" ><font color="red">DISCLAIMER: This page reflects investigation into how EclipseLink technology can used as part of - or benefit from integration with other projects. It does NOT imply any formal certification from EclipseLink on these technologies or make any assumptions on the direction of the API. This page is purely experimental speculation.</font></div> | ||
*This page details initiatives or projects that use or could benefit from using EclipseLink technology. | *This page details initiatives or projects that use or could benefit from using EclipseLink technology. | ||
| Line 5: | Line 5: | ||
==Projects== | ==Projects== | ||
===Projects In Development === | ===Projects In Development === | ||
| + | ====[http://wiki.eclipse.org/EclipseLink/Cloud#Base_Case_1:_Custom_Distributed_RMI Distributed RMI]==== | ||
| + | ====Distributed Automata==== | ||
| + | =====Requirements===== | ||
| + | *This simple application will serve as a test platform to experiment with a distributed SE or EE application so we can test various communication schemes between the physically distributed processing cores. | ||
| + | *A very simple data model consisting of a planar grid of SIMD ALU units will be partitioned among a group of Java Virtual Machines (both local and remote). | ||
| + | *We will not use a 2nd level cache as of yet like Coherence or Terracotta to handle inter-VM synchronization until we understand the problem space | ||
| + | |||
| + | =====Design===== | ||
| + | |||
| + | =====Implementation===== | ||
| + | =====Testing===== | ||
| + | |||
===Projects In Analysis === | ===Projects In Analysis === | ||
===Projects Not Started === | ===Projects Not Started === | ||
| + | ====OpenCL Integration==== | ||
| + | * [http://developer.amd.com/zones/OpenCLZone/Pages/default.aspx OpenCL] is a standard API for general purpose programming across multicore CPU's, Vector based GPU's and other heterogeneous parallel processors. In the event that EclipseLink becomes more ''architecture aware'' and requires the use of possibly '''SIMD''' processing. | ||
| + | ====Java Chip Integration==== | ||
| + | *Develop hardware to directly execute Java bytecode (like the [http://en.wikipedia.org/wiki/ARM9E ARM 9E] via [http://en.wikipedia.org/wiki/Jazelle Jazelle]) | ||
| + | |||
==References== | ==References== | ||
| + | --> | ||