cnderrauber 89faaeba82 Apply ttl check only when authenticate allocation creating (#4526) ...

* Apply ttl check only when authenticate allocation creating

TTL check could reject allocation/persmission refresh in
security enhancement #4505, cause long-live session disconnect
when turn credential is expired.
Only check ttl on allocation creating to prevent abusing leaked
credential but keep long-live session work.

2026-05-15 14:55:05 +08:00

..

prometheus

Some drive-by clean up (#4452)

2026-04-15 12:23:33 +05:30

telemetryfakes

Key telemetry stats worker using combination of roomID, participantID (#4323)

2026-02-16 13:56:13 +05:30

analyticsservice.go

Taking interface{} -> any modernize bits (#4204)

2025-12-28 05:22:12 +05:30

events_test.go

Key telemetry stats worker using combination of roomID, participantID (#4323)

2026-02-16 13:56:13 +05:30

events.go

Rename log field "pID" to "participantID" for consistency (#4365)

2026-03-15 04:32:02 -07:00

stats_test.go

Key telemetry stats worker using combination of roomID, participantID (#4323)

2026-02-16 13:56:13 +05:30

stats.go

Key telemetry stats worker using combination of roomID, participantID (#4323)

2026-02-16 13:56:13 +05:30

statsconn.go

Apply ttl check only when authenticate allocation creating (#4526)

2026-05-15 14:55:05 +08:00

statsworker_test.go

fix stats worker closed condition (#3965)

2025-09-29 02:51:58 -07:00

statsworker.go

Convert sort.Slice -> slices.SortFunc (#4472)

2026-04-23 15:12:24 +05:30

telemetryservice.go

Key telemetry stats worker using combination of roomID, participantID (#4323)

2026-02-16 13:56:13 +05:30