8xFF / 8xFF/atm0s-media-server
feat: Session related events propagation
- Dominant language
- Rust
- Stars
- 329
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
## Description
At present from server end session related events are not propagating to client https://github.com/8xFF/atm0s-media-server/blob/b63e5cfba049b6421cdd576da5e0fb802c012d49/packages/protocol/proto/sdk/session.proto#L199C13-L199C20
Those are also important events from client side. It will be nice to have those.
discussion: https://discord.com/channels/1173844241542287482/1173844241542287485/1266298331609567284
## Steps to Reproduce
1. Step 1
2. Step 2
3. Step 3
## Expected Behavior
Please describe what you expected to happen.
## Actual Behavior
Please describe what actually happened.
## Screenshots
If applicable, add screenshots to help explain the issue.
## Environment
- Operating System:
- Browser (if applicable):
- Version (if applicable):
## Additional Information
Add any other relevant information about the issue here.
Contributor guide
Research direction
The issue points to a specific proto file (packages/protocol/proto/sdk/session.proto) and mentions session-related events not propagating to the client. Start by examining the session.proto file to understand the event definitions and the existing gRPC service. Then, look for the server-side event handling code and the client-side SDK to see where events are sent and received. The goal is to ensure the defined session events are transmitted from server to client.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100