Raja Subramanian 2a6a9b8a4a Grouping all signal messages into participant_signal. (#3801) ...

Currently, it is a bit of a mish-mash
- some compose the message fully and just call send()
- some give parameters and the message is composed in
  participant_signal.go

Was thinking about making an interface for signalling and have v1/v2
impls, but did not want to repeat composing messages if there are common
messages. And some of those function reach into `ParicipantImpl` object
and use information (simple example of p.IsReady()) which would become
more elaborate if the signaller is split out into its own struct.

Maybe, just need to make an interface for the sink and send to the
correct sink based on v1 /v2 signal transport.

But, for now, just grouping all signal messaages in one file
so that it is easier to manage later.

2025-07-18 15:24:52 +05:30

..

typesfakes

Grouping all signal messages into participant_signal. (#3801)

2025-07-18 15:24:52 +05:30

ice.go

implement observability for room metrics (#3712)

2025-06-09 09:32:58 -07:00

interfaces.go

Grouping all signal messages into participant_signal. (#3801)

2025-07-18 15:24:52 +05:30

protocol_version.go

~Send initial participant update only after a participant becomes active.~ - General clean up (#3655)

2025-05-13 14:46:35 +05:30

trafficstats.go

Add back TrafficStats used by cloud. (#2736)

2024-05-27 13:43:20 +05:30