protocol

Files

Raja Subramanian 30cee625bf Adding a simulation option for leave request. (#713 )

* Adding a simulation option for leave request.

@lukasIO I was thinking of making the simulation option
just a `LeaveRequest`. And when simulating, client side
can just set `Action` field of `LeaveRequest`.
But, decided against it as I did not use case for it
and also wanted to keep it simple/specific.

Let me know if I should change that to a generic `LeaveRequest`.
If doing generic `LeaveRequest`, server behaviour would be
1. `Action = DISCONNECT`: server will close the participant and send a
   `LeaveRequest` with `Action = DISCONNECT`.
2. `Action = RESUME`, server will send `LeaveRequest` with `Action = RESUME`
   and it will not include self region in `RegionSettings`.
3. `Action = RECONNECT`, server will send `LeaveRequest` with `Action = RECONNECT`
   and it will not include self region in `RegionSettings`.

As the current simulation is only for full reconnect, it will behave
like #3 above.

Also, this option will be supported in cloud.

Please let me know if I should change this or just leave it as a
boolean.

* generated protobuf

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

2024-05-13 00:06:19 +05:30

livekit_agent.pb.go

allow setting min log level for logger (#705 )

2024-05-06 22:22:14 -07:00

livekit_analytics_grpc.pb.go

analytics: send local room state (#554 )

2023-12-22 18:44:45 -05:00

livekit_analytics.pb.go

allow setting min log level for logger (#705 )

2024-05-06 22:22:14 -07:00

livekit_egress.pb.go

Add RedactAutoEncodedOutput to support redacting auto egress types (#712 )