From 63a9d19cb6ade325fef9534bc0de8e58415df2da Mon Sep 17 00:00:00 2001 From: Javier Montalvo Orus Date: Fri, 30 Mar 2007 17:43:42 +0000 Subject: [PATCH] [170911] [plan] Improve Discovery and Autodetect in RSE --- rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html | 3 +++ 1 file changed, 3 insertions(+) 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 ec2ba2e8f8f..475d3afb8a4 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 @@ -33,6 +33,9 @@ object via its ID.
  • vendor. Your company name, shown in properties dial
  • systemTypeIds. A semi-colon separated list of system type IDs which this subsystem configuration supports. When a user creates a connection, this configuration will only be asked to create a subsystem for connections to systems of these types. Wildcards are supported; in order to register against all system types, specify a single "*". +
  • serviceType. An optional semi-colon separated list of names and transports that can be used to match this service with remotelly advertised services through DNS-SD or any other supported service discovery protocol. +The name would usually be the keyword used by the IANA +or by DNS SRV service types (RFC 2782).
  • category. A name used to categorize this subsystem's functionality. Used by the popupMenus and propertyPages extension points to allow actions and property pages to be scoped to resources shown in subsystems of a particular category. Multiple subsystems can have the same category.