-
Notifications
You must be signed in to change notification settings - Fork 9
Communication protocol for Dive: Messages #226
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
base: main
Are you sure you want to change the base?
Conversation
elviscapiaq
commented
Jun 4, 2025
- Messages (Request/Response) were added for the socket connection.
- Helper functions for messages were added.
A general comment: better to follow the Dive naming convention by adding |
Are things like this written down somewhere? |
not as I know. it is used from the Stadia Dive project, so I tend to follow that to keep the code consistent. |
0ef9bc7
to
2103bd9
Compare
Updated to this naming convention. |
network/messages.h
Outdated
HANDSHAKE_RESPONSE = 2, | ||
PING_MESSAGE = 3, | ||
PONG_MESSAGE = 4, | ||
CAPTURE_REQUEST = 5, |
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.
Which kind of capture is this, PM4 / gfxr? Or is it meant to encompass both?
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.
Actually, it's PM4 capture. We are going to replace the current gRPC implementation, which only performs PM4 capture when using the server. We can discuss Gfxr capture using sockets once this implementation is complete. I've updated the naming to be explicit (e.g., PM4_CAPTURE_REQUEST). Thanks for pointing this out.
0842b42
- Messages (Request/Response) were added for the socket connection. - Helper functions for messages were added.