From 2c6a9629c68b328e28aa1d1447e8f2bd79bd9543 Mon Sep 17 00:00:00 2001 From: David Dykstal Date: Wed, 20 Jun 2007 03:29:10 +0000 Subject: [PATCH] [191588] simplified the team support discussion, removing most of it. --- .../guide/Artifacts.html | 41 ++++-- .../guide/plugin/subsystem.html | 20 ++- .../concepts/cprofile.html | 123 +++++++++--------- .../gettingstarted/gxtending.html | 4 + rse/doc/org.eclipse.rse.doc.user/toc.xml | 2 + 5 files changed, 109 insertions(+), 81 deletions(-) diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/Artifacts.html b/rse/doc/org.eclipse.rse.doc.isv/guide/Artifacts.html index aba5465d642..9e692f537bc 100755 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/Artifacts.html +++ b/rse/doc/org.eclipse.rse.doc.isv/guide/Artifacts.html @@ -4,7 +4,7 @@ - + RSE Artifacts @@ -30,18 +30,24 @@ The RSE's Remote Systems view shows all existing Ho Hosts are objects that are persisted, containing the information needed to access a particular remote host. The view contains a prompt to create new Hosts, and pop-up menu actions to rename, copy, delete, and reorder existing Hosts.

-

Hosts contain attributes, or data, that is saved between sessions of the workbench. These attributes are +

+Hosts contain attributes, or data, that is saved between sessions of the workbench. These attributes are the host name, the remote system's host name and system type, an optional description, and a user Id that is used by default by each subordinate subsystem, at host time. -Underneath, all Hosts are stored via RSE persistence in an Eclipse project named RemoteSystemsConnections, which -the user can enable for team support, allowing Hosts to be shared by a team. +Underneath, all Hosts are stored in profiles by an registered persistence provider.

Profiles

-To facilitate team-shared and user-unique Hosts, -Hosts are owned by profiles. These are simply folders in the RemoteSystemsConnections -project, as it turns out, within which all other data including Hosts are scoped. Internally profiles are realized as +To facilitate sharing Hosts are owned by Profiles. +In 1.0 these were simply folders in the RemoteSystemsConnections +project. With the introduction of persistence providers in 2.0, profiles +can now be persisted in multiple forms - including the 1.0 scheme. +It is our intention to have RSE allow for the sharing of profiles by exporting to and importing from +the file system or from projects in a future release. +

+

+Internally profiles are realized as SystemProfile objects, managed by the SystemProfileManager. For each profile there is also a SystemHostPool object created to manage the Hosts within that profile. There are menu actions for the @@ -53,7 +59,11 @@ By default, there exists a profile named Team, and a profile with a host is created the user is asked to supply this unique name, which defaults to the hostname of their workstation. Whenever a new host is created, the user is prompted for an active profile to contain the new host. Both default profiles are active initially, so all Hosts from each are shown. There is a preferences -setting to show the host names qualified by their profile name. After synchronizing the RemoteSystemsConnections +setting to show the host names qualified by their profile name. +

+ +

Subsystems and subsystem configurations

@@ -98,7 +106,12 @@ remote commands. There is also a Remote Shell view supplied that logs all comman enter a command to be run remotely. The commands all execute within the same shell, and users can launch additional shells for the same host. -

Systems and System Managers

+

+Each subsystem can have a unique user ID, which if not set is inherited from its host, +which in turn if not set is inherited from the +user ID preferences setting for the appropriate system type. +

+

Connector services and their managers

While not seen by the user, subsystem objects are required to return a connectorservice object via the getConnectorService() method. A connectorService object is an object implementing the IConnectorService interface. diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html index 3d7c1ac1daa..e539d35cba4 100755 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html +++ b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html @@ -23,14 +23,20 @@ each created by a subsystem configuration registered with this extension point. as it has only one element, <configuration>, with only a few simple attributes to supply: