mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-07-29 20:05:35 +02:00
[159581] added guide sections for connector services, hosts, services, and subsystems
This commit is contained in:
David Dykstal
parent
deef8e9ad7
commit
4379b98a9c
6 changed files with 70 additions and 22 deletions
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
|
||||
<html>
|
||||
<head>
|
||||
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
|
||||
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
<meta http-equiv="Content-Style-Type" content="text/css">
|
||||
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
|
||||
|
|
@ -10,6 +10,20 @@
|
|||
</head>
|
||||
<body>
|
||||
<h1>RSE Connector Services</h1>
|
||||
<p>
|
||||
Connector Services provide the mechanism for maintaining a connection to a particular remote system, requesting whatever credentials are
|
||||
required for authentication, and for controlling the persistence of those credentials. A connector service is typically created
|
||||
or referenced by a subsystem configuration when a new subsystem instance is being created.
|
||||
</p><p>
|
||||
Every subsystem has a connector service. Some subsystems will share a connector service among themselves.
|
||||
Subsystems that share a connector service all connect and disconnect at the same time.
|
||||
For example, a file subsystem and
|
||||
a shell subsystem that are both using the SSH protocol will share the same connector service instance so that their connections are established and
|
||||
removed at the same time.
|
||||
</p><p>
|
||||
Connector services use credentials providers (see <code>ICredentialsProvider</code>) to establish any credentials needed for authentication to a
|
||||
remote system.
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
|
||||
<html>
|
||||
<head>
|
||||
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
|
||||
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
<meta http-equiv="Content-Style-Type" content="text/css">
|
||||
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
|
||||
|
|
@ -10,6 +10,18 @@
|
|||
</head>
|
||||
<body>
|
||||
<h1>RSE Hosts</h1>
|
||||
<p>
|
||||
Hosts, sometimes called "connections", are visible as the top level entities shown in the Remote Systems view.
|
||||
Hosts are always created referencing a system type.
|
||||
The system type determines the kinds of services that will be available to that host.
|
||||
System types are defined by the <code>org.eclipse.rse.core.systemTypes</code> extension point, which lists the <code>subsystemConfigurations</code>
|
||||
that are valid for type.
|
||||
</p><p>
|
||||
Once instantiated, hosts can be connected to their target systems.
|
||||
This causes the connector services associated with
|
||||
the subsystems belonging to that host to request connection.
|
||||
Disconnect works similarly.
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
|
||||
<html>
|
||||
<head>
|
||||
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
|
||||
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
<meta http-equiv="Content-Style-Type" content="text/css">
|
||||
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
|
||||
|
|
@ -10,6 +10,24 @@
|
|||
</head>
|
||||
<body>
|
||||
<h1>RSE Services</h1>
|
||||
<p>
|
||||
RSE is built on top of a service layer that provides services that access the remote systems.
|
||||
These service implementations are typically protocol-specific but will obey an interface that defined for that paricular service.
|
||||
For example, a file service will obey the interface defined in the package
|
||||
<code>org.eclipse.rse.services.files</code>, but there
|
||||
exist implementations for the dstore, FTP, and SSH protocols.
|
||||
</p>
|
||||
<p>
|
||||
RSE supplies service definitions for a file service, a shell service for submitting remote commands, a search service, and a process service.
|
||||
Implementers that which to use different protocols than the ones supplied should use the existing service definitions to fit into the current
|
||||
structure.
|
||||
</p>
|
||||
<p>
|
||||
It is not absolutely necessary to have a services layer.
|
||||
Implementers of subsystems that provide access to resources that in narrow domains
|
||||
could forgo the creation of explicit service classes and embed the
|
||||
support directly in the subsystem.
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
|
||||
<html>
|
||||
<head>
|
||||
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
|
||||
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
<meta http-equiv="Content-Style-Type" content="text/css">
|
||||
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
|
||||
|
|
@ -10,6 +10,27 @@
|
|||
</head>
|
||||
<body>
|
||||
<h1>RSE Subsystems</h1>
|
||||
<p>
|
||||
Subsystems provide a layer of abstraction on the set of services provided at lower layers.
|
||||
Subsystems make remote resources individually visible to their clients and expose the relationships among these resources - such as the parent-child
|
||||
relationship between directories and files on a remote file system.
|
||||
</p>
|
||||
<p>
|
||||
There should typically be only one subsystem implementation for each type of remote resource.
|
||||
Minor differences between remote systems or
|
||||
the protocols required to access them should be provided by different
|
||||
implementations of an underlying service.
|
||||
For example, RSE provides a single
|
||||
exemplary file subsystem, but that file subsystem uses different file services to use different remote file access protocols.
|
||||
The duty of tieing a subsystem to its underlying service goes to the subsystem configuration.
|
||||
</p>
|
||||
<p>
|
||||
A subsystem configuration creates subsystems of the kind it understands and, in addition, create them with the appropriate
|
||||
underlying service if there is one. These configuration classes are registered with RSE using the
|
||||
<code>org.eclipse.rse.core.subsystemConfigurations</code> extension point.
|
||||
</p>
|
||||
<p>
|
||||
RSE supplies ready-made subsystems for files, command execution, and processes.
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,16 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
|
||||
<html>
|
||||
|
||||
<head>
|
||||
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
<meta http-equiv="Content-Style-Type" content="text/css">
|
||||
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
|
||||
<title>RSE UI</title>
|
||||
<link rel="stylesheet" type="text/css" href="../book.css">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>RSE UI</h1>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -12,7 +12,6 @@
|
|||
<topic label="Subsystems" href="guide/rse_int_subsystems.html"/>
|
||||
<topic label="Connector Services" href="guide/rse_int_connectorservices.html"/>
|
||||
<topic label="Hosts" href="guide/rse_int_hosts.html"/>
|
||||
<topic label="User Interface" href="guide/rse_int_ui.html"/>
|
||||
</topic>
|
||||
<topic label="Using the RSE API" href="guide/usingAPIs.html">
|
||||
<topic label="RSE User Interface API" href="guide/api/uiAPI.html" />
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue