| 17 |
<ol> |
<ol> |
| 18 |
<li>Updates for very large products (e.g. 500+ plug-ins) can also be large. |
<li>Updates for very large products (e.g. 500+ plug-ins) can also be large. |
| 19 |
I/T support teams may not like the idea of hundreds of developers individually |
I/T support teams may not like the idea of hundreds of developers individually |
| 20 |
downloading 500MEG updates to their individual machines. In addition to |
downloading 500MEG updates to their individual machines. In addition to the |
| 21 |
bandwidth hit, such large download request may fail, leading to repeated |
bandwidth hit, such a large download request may fail, leading to repeated |
| 22 |
attempts and increased developers' downtime.</li> |
attempts and increased developers' downtime.</li> |
| 23 |
<li>Some companies explicitly don't want the developers downloading updates |
<li>Some companies explicitly don't want the developers downloading updates |
| 24 |
directly from the Internet. For example, they can set up a local support team |
directly from the Internet. For example, they can set up a local support team |
| 30 |
way of letting users know that updates are available.</li> |
way of letting users know that updates are available.</li> |
| 31 |
</ol> |
</ol> |
| 32 |
<h2>2. The Proposal</h2> |
<h2>2. The Proposal</h2> |
| 33 |
<p>The proposed solution in Eclipse 3.0 comprises of three new capabilities that |
<p>The proposed solution in Eclipse 3.0 consists of three new capabilities that |
| 34 |
together address all of the above problems. </p> |
together address all of the above problems. </p> |
| 35 |
<h3>2.1 Support for creating local (proxy) update sites</h3> |
<h3>2.1 Support for creating local (proxy) update sites</h3> |
| 36 |
<p>First step for a product administrator would be to set up a local Eclipse |
<p>First step for a product administrator would be to set up a local Eclipse |
Parent Directory
| 
Revision Log
| 
Patch