Skip to content

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

elviscapiaq
Copy link
Collaborator

  • Messages (Request/Response) were added for the socket connection.
  • Helper functions for messages were added.

@wangra-google
Copy link
Collaborator

A general comment: better to follow the Dive naming convention by adding m_ prefix to all class members

@footballhead
Copy link
Collaborator

A general comment: better to follow the Dive naming convention by adding m_ prefix to all class members

Are things like this written down somewhere?

@wangra-google
Copy link
Collaborator

A general comment: better to follow the Dive naming convention by adding m_ prefix to all class members

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.

@elviscapiaq
Copy link
Collaborator Author

A general comment: better to follow the Dive naming convention by adding m_ prefix to all class members

Updated to this naming convention.

RenfengLiu
RenfengLiu previously approved these changes Jun 5, 2025
wangra-google
wangra-google previously approved these changes Jun 5, 2025
HANDSHAKE_RESPONSE = 2,
PING_MESSAGE = 3,
PONG_MESSAGE = 4,
CAPTURE_REQUEST = 5,
Copy link
Collaborator

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?

Copy link
Collaborator Author

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.

- Messages (Request/Response) were added for the socket connection.
- Helper functions for messages were added.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants