Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoreutarass2008-02-15 21:45:25 +0000
committereutarass2008-02-15 21:45:25 +0000
commit5ac36a50b1e59e1c89d7f8c4a549f52205928f66 (patch)
tree9cd06cefbc27700422054a451bf990a14462d711 /docs/TCF Service - System Monitor.html
parent6459bb640308817d92790bb1b7b61348c5418ba8 (diff)
downloadorg.eclipse.tcf-5ac36a50b1e59e1c89d7f8c4a549f52205928f66.tar.gz
org.eclipse.tcf-5ac36a50b1e59e1c89d7f8c4a549f52205928f66.tar.xz
org.eclipse.tcf-5ac36a50b1e59e1c89d7f8c4a549f52205928f66.zip
The new version 0.2.0 of Target Communication Framework has major improvements
in several areas: 1. Target agent improvements: a. Generic communication and discovery code is separated from TCP/IP specific code. Now the agent can support multiple transport protocols simultaneously. b. Multiple agents can run on same host. One of them is automatically elected to be a master discovery server. c. Agent now can have different sets of services on different server sockets. 2. TCF debugger prototype is reworked in order to improve remote data caching logic. Now, for example, stack frame attributes, like source code position, are reused from cache when a thread is suspended; only frames that did not change during thread execution are reused - usually bottom part of a stack. 3. DSF/TCF integration is extended to include TCF implementation of several DSF services. 4. Many bugs are fixed in the code.
Diffstat (limited to 'docs/TCF Service - System Monitor.html')
-rw-r--r--docs/TCF Service - System Monitor.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/TCF Service - System Monitor.html b/docs/TCF Service - System Monitor.html
index 882e91094..fb9dbd1ed 100644
--- a/docs/TCF Service - System Monitor.html
+++ b/docs/TCF Service - System Monitor.html
@@ -503,7 +503,7 @@ R • <i>&lt;token&gt;</i> • <i>&lt;error report&gt;</i> • <i>&lt;array of string&
<font color=#3F5FBF>/** Scheduling policy */</font>
PROP_POLICY = "Policy";
-
+
<font color=#3F5FBF>/**
* A context corresponds to an execution thread, process, address space, etc.
* A context can belong to a parent context. Contexts hierarchy can be simple
@@ -514,7 +514,7 @@ R • <i>&lt;token&gt;</i> • <i>&lt;error report&gt;</i> • <i>&lt;array of string&
* attributes and functionality, which is relevant to that service.
*/</font>
<font color=#7F0055>interface</font> SysMonitorContext {
-
+
<font color=#3F5FBF>/**
* Get context ID.
* Same as getProperties().get(“ID”)

Back to the top