trace-server-protocol icon indicating copy to clipboard operation
trace-server-protocol copied to clipboard

Specification of the Trace Server Protocol (TSP)

Results 24 trace-server-protocol issues
Sort by recently updated
recently updated
newest added

With this it's possible to close an experiment on the server. Upon reception of the command the server can dispose allocated resources hence the client doesn't need them anymore. UI...

PUT for experiments command should not use actions in payload (see below). To add or remove traces provide a list of traces UUIDs in the payload and the server needs...

bug

This endpoint can be used to close the experiment and upon reception of the message, the server can dispose can dispose allocated resources. The Trace Compass server will dispose the...

enhancement

My interpretation of the TSP. A tentative description of what it is, what it aims to accomplish and the use cases it aims to solve. Some initial guidelines to follow...

- What is a gap state? - How and when they are supposed to created in the server? - How they are supposed to be used in the client? -...

Add a vision statement for implementers to understand the underlying logic.

- Rename operation "putExperiment" to "updateExperiment" - Remove actions to remove or add traces - Move name query parameter to payload fixes #69 Signed-off-by: Bernd Hufmann

It would be interesting to get trace specific one shot data, e.g. : * Host Name * CPU architecture (number of cores/bigLITTLE?) * System Memory * GPUs available (number of...

Right now the `parentId` in the EntryModel is specified as optional and if not present it means that the Entry doesn't have a parent. Being optional has the advantage that...

Fixes #35 With this, it is expected that column and entry descriptions may contain an optional typing option, to explain what the data type is and, if available, what unit...