-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update README.md with vision statement #89
base: master
Are you sure you want to change the base?
Conversation
Add a vision statement for implementers to understand the underlying logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
||
* Keep things as imutable as possible | ||
* A trace can be queried for any UI elements. | ||
* UI elements can be but should not be limited to charts, graphs, trees and more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Markdownlint has issues with this reformatted line and the few ones below (8 and 9).
@@ -1,5 +1,17 @@ | |||
# trace-server-protocol | |||
|
|||
The Trace Server Protocol is a protocol designed to allow frontend visualizers to be decoupled from backend. It allows the frontend to query resources in a RESTful way. The guiding principles: | |||
|
|||
* Keep things as imutable as possible |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
immutable
The Trace Server Protocol is a protocol designed to allow frontend visualizers to be decoupled from backend. It allows the frontend to query resources in a RESTful way. The guiding principles: | ||
|
||
* Keep things as imutable as possible | ||
* A trace can be queried for any UI elements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any UI element.
@@ -1,5 +1,17 @@ | |||
# trace-server-protocol | |||
|
|||
The Trace Server Protocol is a protocol designed to allow frontend visualizers to be decoupled from backend. It allows the frontend to query resources in a RESTful way. The guiding principles: | |||
|
|||
* Keep things as imutable as possible |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as possible.
* Filtering on the server side may produce additional UI elements. | ||
* The data type is delivered to the client so the client can remain as lightweight as possible. | ||
|
||
The initial design is base on the Eclipse Trace Compass backend and the theia-trace-extension frontend, however this protocol is agnostic and all changes will be considered and suggestions are welcomed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is based on
** The data type is delivered to the client so the client can remain as lightweight as possible. | ||
* UI elements can be but should not be limited to charts, graphs, trees and more. | ||
* Filtering on the server side may produce additional UI elements. | ||
* The data type is delivered to the client so the client can remain as lightweight as possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The second commit should be squashed into the first/base one, here in this specific case.
@@ -1,5 +1,17 @@ | |||
# trace-server-protocol | |||
|
|||
The Trace Server Protocol is a protocol designed to allow frontend visualizers to be decoupled from backend. It allows the frontend to query resources in a RESTful way. The guiding principles: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about the RESTful way,
- as TSP currently bundles a lot of request payload into the body.
- Recent cross-team discussions also highlighted the current limitations in terms of resource/entity modeling, starting at the request URI level.
- We also mentioned the domain language which could improve from an ubiquity perspective.
- All in all, this README may mention the REST/http basis of TSP, without claiming REST-fullness, I think.
@@ -1,5 +1,17 @@ | |||
# trace-server-protocol |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit message(s) and PR header are missing a Signed-off-by
footer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addendum: commit message's body line needs a wrap to max 72 chars, per guideline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comments added herein.
Add a vision statement for implementers to understand the underlying logic.