platform-core-home/runtime/index.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.2, Wed Nov 26 13:46:29 2003 UTC revision 1.3, Wed Nov 26 14:52:14 2003 UTC
# Line 22  Line 22 
22                  </table>                  </table>
23    
24    
25  <p>Eclipse currently uses a home-grown runtime model. That is, the runtime model/mechanism  <p>Eclipse originally used a home-grown runtime model. That is, the runtime model/mechanism
26    was designed and implemented specifically for Eclipse. This is good in that    was designed and implemented specifically for Eclipse. This was good in that
27    it has been highly optimized and tailored. It is less than optimal in that there    it was highly optimized and tailored. It was less than optimal in that there
28    are many issues which are complicated and having a unique runtime mechanism    are many issues which are complicated and having a unique runtime mechanism
29    does not allow us to reuse the work done in other areas (e.g., OSGi, Avalon,    does not allow us to reuse the work done in other areas (e.g., OSGi, Avalon,
30    JMX, ...). In particular we are looking for a runtime that has a strong specification,    JMX, ...). To address this, we went looking for a runtime that has a strong
31    a good component model, supports dynamic behaviour, and is reasonably similar    specification, a good component model, supports dynamic behaviour, and is reasonably
32    to that of Eclipse.</p>    similar to that of Eclipse.</p>
33  <p>This last point bears some discussion. While we would like to start with a  <p>This last point bears some discussion. While we would like to start with a
34    clean slate and adopt/design a runtime which satisfies everyone's wish list,    clean slate and adopt/design a runtime which satisfies everyone's wish list,
35    pragmatically, it must still be possible to run old plug-ins on the new runtime    pragmatically, it must still be possible to run old plug-ins on the new runtime
36    with confidence. That is, the new runtime cannot be so completely different    with confidence. That is, the new runtime cannot be so completely different
37    so as to make this difficult/totally inefficient/impossible.</p>    so as to make this difficult/totally inefficient/impossible.</p>
38  <p>Our attention has focussed on <a href="http://www.osgi.org">OSGi</a> and we  <p>To that end, we have implemented a plug-compatible runtime for Eclipse based
39    have implemented a plug-compatible runtime for Eclipse based on the OSGi specification.    on the OSGi specification. Consult the resources below for more information.</p>
   Consult the resources below for more information.</p>  
40  <table border=0 cellspacing=5 cellpadding=2 width="100%" >  <table border=0 cellspacing=5 cellpadding=2 width="100%" >
41    <tr>    <tr>
42      <td align=LEFT valign=TOP colspan="2" bgcolor="#0080C0"><b><font color="#FFFFFF">      <td align=LEFT valign=TOP colspan="2" bgcolor="#0080C0"><b><font color="#FFFFFF">
Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3