Skip to main content
Jump to: navigation, search

Difference between revisions of "E4/Connection Frameworks"

< E4
 
Line 1: Line 1:
 
&larr;[[E4/Project Proposal | Back to E4/Project Proposal page]]
 
&larr;[[E4/Project Proposal | Back to E4/Project Proposal page]]
  
 +
=Shared, Cross-Project Connection Frameworks=
 +
One of the issues across some of the major Eclipse projects is the issue of cross-project integration. This is especially evident in terms of connection frameworks.
 +
 +
The Eclipse ecosystem has many different types of "connection" frameworks. The CVS (Eclipse Platform), Remote Systems Explorer (DSDP-TM), Web (WTP), Communications (ECF), and Database Development (DTP) perspectives all have their own server/system connection management user interfaces and connection frameworks. WTP has been working with DTP to handle management of database connections, which is great, but it's just the tip of the iceberg.
 +
 +
Within e4, we have a chance to settle on a common framework for connection management and its associated UI. This would not only help out the user with a common look and feel across the Eclipse ecosystem for connecting to various systems, but it would allow adopters and extenders to take advantage of this common framework so they too would fit into the Eclipse-iverse more seamlessly to their own users.
 +
 +
The connection framework within DTP, though used primarily for JDBC database connections at this point, has been used with great success in many other ways by Sybase products to connect to file systems, application servers, UDDI and LDAP repositories, and so on. I think it has great potential to fill the need for a common connection framework in e4.
 +
 +
However, integrating will the other projects in Eclipse will be tricky at best and require a great deal of collaboration from many interested parties.
  
 
[[Category:E4]]
 
[[Category:E4]]

Revision as of 15:41, 21 August 2008

Back to E4/Project Proposal page

Shared, Cross-Project Connection Frameworks

One of the issues across some of the major Eclipse projects is the issue of cross-project integration. This is especially evident in terms of connection frameworks.

The Eclipse ecosystem has many different types of "connection" frameworks. The CVS (Eclipse Platform), Remote Systems Explorer (DSDP-TM), Web (WTP), Communications (ECF), and Database Development (DTP) perspectives all have their own server/system connection management user interfaces and connection frameworks. WTP has been working with DTP to handle management of database connections, which is great, but it's just the tip of the iceberg.

Within e4, we have a chance to settle on a common framework for connection management and its associated UI. This would not only help out the user with a common look and feel across the Eclipse ecosystem for connecting to various systems, but it would allow adopters and extenders to take advantage of this common framework so they too would fit into the Eclipse-iverse more seamlessly to their own users.

The connection framework within DTP, though used primarily for JDBC database connections at this point, has been used with great success in many other ways by Sybase products to connect to file systems, application servers, UDDI and LDAP repositories, and so on. I think it has great potential to fill the need for a common connection framework in e4.

However, integrating will the other projects in Eclipse will be tricky at best and require a great deal of collaboration from many interested parties.

Back to the top