platform-core-home/documents/3.1/large_scale_issues.html

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

revision 1.7, Fri Jan 14 19:17:09 2005 UTC revision 1.8, Thu Feb 24 19:27:05 2005 UTC
# Line 9  Line 9 
9  <table width="100%">  <table width="100%">
10  <tr><td style="background:#0080C0"><b><span style="color:white">Large-scale development issues</span></b></td></tr>  <tr><td style="background:#0080C0"><b><span style="color:white">Large-scale development issues</span></b></td></tr>
11  </table>  </table>
12  <font size="-1">Last modified: January 14, 2005</font>  <font size="-1">Last modified: February 24, 2005</font>
13  <p>  <p>
14  One of the major development themes for Eclipse 3.1 is to improve support for  One of the major development themes for Eclipse 3.1 is to improve support for
15  "Large-scale development" in Eclipse. This includes improving collaboration for  "Large-scale development" in Eclipse. This includes improving collaboration for
# Line 44  Line 44 
44          in memory about the synchronization and "dirty" state of each resource. Explore          in memory about the synchronization and "dirty" state of each resource. Explore
45          reducing the footprint of this data or using lazy caching to only bring this information          reducing the footprint of this data or using lazy caching to only bring this information
46          into memory when needed.          into memory when needed.
47  <li><img src="../../images/progress.gif" height="5" width="14" border="0">  <li><img src="../../images/ok.gif"  height="10" width="10" border="0">
48          Message bundles. Most plug-ins store translated strings in <tt>ResourceBundle</tt>          Message bundles (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37712">37712</a>).
49            Most plug-ins store translated strings in <tt>ResourceBundle</tt>
50          objects.  These bundles are not space-efficient, and often use lengthy string-based          objects.  These bundles are not space-efficient, and often use lengthy string-based
51          keys for message lookup.  Explore a more efficient representation, integer-based keys,          keys for message lookup.  Explore a more efficient representation, integer-based keys,
52          or a disk-based bundle for infrequently used messages.          or a disk-based bundle for infrequently used messages.
# Line 65  Line 66 
66          all the files and to gather local information such as time stamps. This project          all the files and to gather local information such as time stamps. This project
67          discovery can be moved into a background thread.          discovery can be moved into a background thread.
68  </li>  </li>
69  <li><img src="../../images/progress.gif" height="5" width="14" border="0">  <li><img src="../../images/ok.gif"  height="10" width="10" border="0">
70          Resource copy, move, and delete.  Most operations that act on trees of resources          Resource copy, move, and delete.  Most operations that act on trees of resources
71          still cannot be run in the background.  When these operations take a long time,          still cannot be run in the background.  When these operations take a long time,
72          the user is forced to wait until they complete. These should be converted to "user" jobs          the user is forced to wait until they complete. These should be converted to "user" jobs
73          that can optionally be run in the background.          that can optionally be run in the background.
74  </li>  </li>
75  <li>Recursive deletion.  Java provides no API for recursively deleting a directory  <li><font class="indexsub" color="#8080ff">[&gt;3.1]</font>
76    Recursive deletion      (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=10628">10628</a>).
77    Java provides no API for recursively deleting a directory
78  containing files and other directories. This means deleting a large resource tree  containing files and other directories. This means deleting a large resource tree
79  requires two native I/O calls per directory (one to list the children, one to delete), and  requires two native I/O calls per directory (one to list the children, one to delete), and
80  one native I/O call per file.  This particularly impacts compilation, which often needs  one native I/O call per file.  This particularly impacts compilation, which often needs
Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8