1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-02 22:55:26 +02:00

Renamed remaining "Riverbed"s to "DSF"s.

This commit is contained in:
Pawel Piech 2006-08-16 16:48:25 +00:00
parent ec84c5494b
commit fb0fd74800
12 changed files with 33 additions and 33 deletions

View file

@ -1,6 +1,6 @@
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Riverbed Plug-in
Bundle-Name: DSF Plug-in
Bundle-SymbolicName: org.eclipse.dd.dsf
Bundle-Version: 1.0.0
Bundle-Activator: org.eclipse.dd.dsf.DsfPlugin

View file

@ -18,7 +18,7 @@ import org.eclipse.core.runtime.Status;
import org.eclipse.dd.dsf.DsfPlugin;
/**
* Default implementation of a Riverbed executor interfaces, based on the
* Default implementation of a DSF executor interfaces, based on the
* standard java.util.concurrent.ThreadPoolExecutor.
*/
@ -29,7 +29,7 @@ public class DefaultDsfExecutor extends ScheduledThreadPoolExecutor
Thread fThread;
public Thread newThread(Runnable r) {
assert fThread == null; // Should be called only once.
fThread = new Thread(new ThreadGroup("Riverbed Thread Group"), r, "Riverbed Dispatch Thread", 0);
fThread = new Thread(new ThreadGroup("DSF Thread Group"), r, "DSF Dispatch Thread", 0);
return fThread;
}
}

View file

@ -16,7 +16,7 @@ import org.eclipse.core.runtime.Status;
import org.eclipse.dd.dsf.DsfPlugin;
/**
* Base class for Riverbed service method-completion callbacks. By default
* Base class for DSF service method-completion callbacks. By default
* all callbacks that indicate a complition of a method contain the status
* of the result.
* <br>NOTE: Access to the status data is not synchronized, so

View file

@ -13,9 +13,9 @@ package org.eclipse.dd.dsf.concurrent;
/**
* A DSF-instrumented alternative to the Runnable interface.
* <p>
* While it is perfectly fine for clients to call the Riverbed executor with
* an object only implementing the Runnable interface, the RbRunnable is a
* place holder for future tracing enhancments for Riverbed.
* While it is perfectly fine for clients to call the DSF executor with
* an object only implementing the Runnable interface, the DsfRunnable is a
* place holder for future tracing enhancments for DSF.
*/
abstract public class DsfRunnable implements Runnable {
}

View file

@ -22,7 +22,7 @@ import org.eclipse.dd.dsf.DsfPlugin;
* <p>
* Certain complex tasks require multiple commands to be executed in a chain,
* because for example result of one command is used as input into another
* command. The typical Riverbed pattern of solving this problem is the following:
* command. The typical DSF pattern of solving this problem is the following:
* <li>
* <br> 1. original caller passes a Done callback to a method and invokes it
* <br> 2. the method is executed by a subsystem
@ -49,7 +49,7 @@ abstract public class DsfSequence {
* The abstract class that each step has to implement
* <br>FIXME: convert execute() and rollBacl() to take "done" as an argument.
* This way we can make step a static class, and make its paradigm
* more consistent with rest of Riverbed.
* more consistent with rest of DSF.
*/
abstract public class Step {
public void execute() { stepFinished(); }
@ -69,7 +69,7 @@ abstract public class DsfSequence {
/**
* Default constructor. If this constructor is used, the steps need to be initialized
* before the sequence can be invoked.
* @param executor the Riverbed executor which will be used to invoke all steps
* @param executor the DSF executor which will be used to invoke all steps
*/
public DsfSequence(DsfExecutor executor) {
this(executor, null);
@ -77,7 +77,7 @@ abstract public class DsfSequence {
/**
* Constructor that initialized the steps.
* @param executor the Riverbed executor which will be used to invoke all steps
* @param executor the DSF executor which will be used to invoke all steps
* @param steps sequence steps
*/
public DsfSequence(DsfExecutor executor, Step[] steps) {
@ -85,7 +85,7 @@ abstract public class DsfSequence {
fSteps = steps;
}
/** Returns the riverbed executor for this sequence */
/** Returns the DSF executor for this sequence */
public DsfExecutor getExecutor() { return fExecutor; }
/**
@ -119,7 +119,7 @@ abstract public class DsfSequence {
/**
* Returns index of the step that is currently being executed.
* <br>NOTE: After sequence is invoked, this method should be called
* only in the Riverbed executor thread.
* only in the DSF executor thread.
* @return
*/
public int getCurrentIdx() { return fCurrentStepIdx; }
@ -150,9 +150,9 @@ abstract public class DsfSequence {
}
/**
* Submits this sequence to the Riverbed executor, and blocks waiting for the
* Submits this sequence to the DSF executor, and blocks waiting for the
* sequence to complete.
* <br>NOTE: This method is NOT to be called on the Riverbed executor thread.
* <br>NOTE: This method is NOT to be called on the DSF executor thread.
*/
public synchronized void invoke() {
assert !fExecutor.isInExecutorThread() :

View file

@ -16,7 +16,7 @@ public interface IBackEndProcess extends IDsfService {
* same time, a service property is needed to allow clients to distinguish
* between them.
*/
static final String PROCESS_ID = "org.eclipse.dsdp.riverbed.debug.BackendProcess.PROCESS_ID";
static final String PROCESS_ID = "org.eclipse.dsdp.DSF.debug.BackendProcess.PROCESS_ID";
/**
* Event indicating that the back end process has terminated.

View file

@ -13,7 +13,7 @@ import org.eclipse.dd.dsf.model.IDataModelService;
* Debugger service representing module handling logic of a debugger.
* <br>
* TODO: I meant this as a replacement for Application service as well as the
* registry API in Riverbed 1. But I still don't fully understand the format
* registry API in DSF 1. But I still don't fully understand the format
* of the symbol data that is stored in the registry, so that needs to be added
* to this interface.
*/

View file

@ -14,7 +14,7 @@ import org.eclipse.dd.dsf.concurrent.GetDataDone;
import org.eclipse.dd.dsf.service.IDsfService;
/**
* Interface for Riverbed services that provide model data to clients.
* Interface for DSF services that provide model data to clients.
* <p>
* For completeness this service interface derives from <code>IDataModelData</data>
* and has a method which allows clients to retrieve the DMC that represents the

View file

@ -22,8 +22,8 @@ import org.osgi.framework.ServiceRegistration;
/**
* Standard base implementation of the Riverbed service. This is a convinience
* class that provides the basic functionality that all Riverbed services have
* Standard base implementation of the DSF service. This is a convinience
* class that provides the basic functionality that all DSF services have
* to implement.
*/
abstract public class AbstractDsfService

View file

@ -19,7 +19,7 @@ import org.osgi.framework.InvalidSyntaxException;
import org.osgi.framework.ServiceReference;
/**
* Convenience class to help track Riverbed services that a given
* Convenience class to help track DSF services that a given
* client needs to use. This class is similar to the standard OSGI
* org.osgi.util.tracker.ServiceTracker class, with a few differences:
* <br>1. This class is assumed to be accessed by a single thread hence it
@ -28,7 +28,7 @@ import org.osgi.framework.ServiceReference;
* <br>2. This class is primarily designed to track multiple services of
* different type (class), while OSGI ServiceTracker is designed to work with
* single class type, with optional filtering options.
* <br>3. This class uses knowledge of Riverbed sessions to help narrow down
* <br>3. This class uses knowledge of DSF sessions to help narrow down
* service references.
* <br>4. OSGI Service tracker explicitly listens to OSGI service
* startup/shutdown events and it will clear a reference to a service as
@ -76,7 +76,7 @@ public class DsfServicesTracker {
/**
* Only constructor.
* @param bundleContext Context of the plugin that the client lives in.
* @param sessionId The Riverbed session that this tracker will be used for.
* @param sessionId The DSF session that this tracker will be used for.
*/
public DsfServicesTracker(BundleContext bundleContext, String sessionId) {
fBundleContext = bundleContext;

View file

@ -32,12 +32,12 @@ import org.eclipse.dd.dsf.concurrent.DsfRunnable;
import org.osgi.framework.Filter;
/**
* Class to manage Riverbed sessions. A Riverbed session is a way to
* associate a set of Riverbed services that are running simultaneously and
* Class to manage DSF sessions. A DSF session is a way to
* associate a set of DSF services that are running simultaneously and
* are interacting with each other to provide a complete set of functionality.
* <p>
* Properties of a session are following:
* <br>1. Each session is associated with a single Riverbed executor, although there
* <br>1. Each session is associated with a single DSF executor, although there
* could be multiple sessions using the same executor.
* <br>2. Each session has a unique String identifier, which has to be used by
* the services belonging to this session when registering with OSGI services.
@ -135,7 +135,7 @@ public class DsfSession
* Starts and returns a new session instance. This method can be called on any
* thread, but the session-started listeners will be called using the session's
* executor.
* @param executor The Riverbed executor to use for this session.
* @param executor The DSF executor to use for this session.
* @return instance object of the new session
*/
public static DsfSession startSession(DsfExecutor executor) {
@ -214,7 +214,7 @@ public class DsfSession
/** Returns the ID of this session */
public String getId() { return fId; }
/** Returns the Riverbed executor of this session */
/** Returns the DSF executor of this session */
public DsfExecutor getExecutor() { return fExecutor; }
/**
@ -241,7 +241,7 @@ public class DsfSession
/**
* Retrieves and increments the startup counter for services in this session.
* Riverbed services should retrieve this counter when they are initialized,
* DSF services should retrieve this counter when they are initialized,
* and should return it through IService.getStartupNumber(). This number is then
* used to prioritize service events.
* @return current startup counter value

View file

@ -16,7 +16,7 @@ import org.eclipse.dd.dsf.concurrent.Done;
import org.eclipse.dd.dsf.concurrent.DsfExecutor;
/**
* The inteface that all Riverbed services must implement. It only privides a
* The inteface that all DSF services must implement. It only privides a
* few features to help manage and identify the servies using the OSGI services
* framework.
* <p>
@ -27,8 +27,8 @@ import org.eclipse.dd.dsf.concurrent.DsfExecutor;
* additional properties should be used when registering the service to allow clients
* to uniquely identify the services.
* <p>
* By convention, all methods of Riverbed services can be called only on the dispatch
* thread of the Riverbed executor that is associated with the service. If a
* By convention, all methods of DSF services can be called only on the dispatch
* thread of the DSF executor that is associated with the service. If a
* service exposes a method that is to be called on non-dispatch thread, it should
* be documented so.
*
@ -40,7 +40,7 @@ public interface IDsfService {
/**
* Property name for the session-id of this service. This property should be set by
* all Riverbed services when they are registered with OSGI service framework.
* all DSF services when they are registered with OSGI service framework.
*/
static String PROP_SESSION_ID = "org.eclipse.dd.dsf.service.IService.session_id";