platform-core-home/plan_team_integration.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.1 - (view) (download) (as text)

1 : dj 1.1 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
2 :     <html>
3 :     <head>
4 :     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5 :     <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
6 :     <title>Team/Resource Integration Details</title>
7 :     <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
8 :     </head>
9 :     <body text="#000000" bgcolor="#FFFFFF">
10 :     &nbsp;
11 :     <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
12 :     <tr>
13 :     <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF">Team/Resource
14 :     Integration Details</font></font></b></td>
15 :     </tr>
16 :     <tr>
17 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
18 :     <td WIDTH="98%">
19 :     <p><b>Team/Resource Integration </b>(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37722">37722</a>,
20 :     described in detail <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/team3.0/resources.html">here</a>)</p>
21 :     <p><i>Questions and Issues:</i></p>
22 :     <ul>
23 :     <li>How to manage the file system provider mapping to the resources?
24 :     <ul>
25 :     <li>Needs to be performant.</li>
26 :     </ul>
27 :     </li>
28 :     <li>How is this information persisted?</li>
29 :     <li>Should this information be shared in the repository?</li>
30 :     <li>What differentiates a project from a folder?</li>
31 :     <li>How do we store folder-level metadata? (do we need to do this?)</li>
32 :     <li>How do we handle linked resources?</li>
33 :     <li>How do we provide access to the Core library calls?</li>
34 :     <li>Do we need startup/shutdown lifecycle events to allow for cleanup?</li>
35 :     <li>How do we deal with missing providers?</li>
36 :     <li>DefaultProvider could be an abstract class for others to inherit from.</li>
37 :     <li>Register data providers via an extension point.</li>
38 :     </ul>
39 :     <p>&nbsp;</p>
40 :     </td>
41 :     </tr>
42 :     </table>
43 :    
44 :     </body>
45 :     </html>