Raja Subramanian dc9f16f350 Do not block on down track close with flush. (#2201) ...

* Do not block on down track close with flush.

When publisher removes all subscribers, publisher side should
not be blocked for long. With close with flush, it could happen
if there a lot of bunch of subscribers.

So, when is expected, run it in a goroutine like it is done in
subscription manager.

Not moving the entire `RemoveSubscriber` bit to subscription manager as
there are two bits which are not tracked now
- mime type
- willBeResumed
Those two would have to be tracked in track manager and notified to
subscription manager so that it can act for that mine and if the track
will be resumed or not. As that touch more parts and could get
complicated, doing the simpler thing of cloning behaviour from
subscription manager for now.

* clean up

* code readability

2023-10-30 12:31:00 +05:30

..

clientconfiguration

Disable h264 for android firefox (#2190)

2023-10-27 14:47:36 +08:00

config

Add configuration to limit MaxBufferedAmount for data channel (#2170)

2023-10-23 15:03:58 +08:00

routing

update psrpc (#2188)

2023-10-25 20:20:49 -07:00

rtc

Do not block on down track close with flush. (#2201)

2023-10-30 12:31:00 +05:30

service

clean up ioInfo (#2195)

2023-10-26 13:32:31 -07:00

sfu

Mark packet relevant only when current layer is valid. (#2200)

2023-10-30 00:34:17 +05:30

telemetry

preallocate prometheus packet counters (#1942)

2023-08-08 01:06:14 -07:00

testutils

Adding license notices (#1913)

2023-07-27 16:43:19 -07:00

utils

Integrate logger components (#1933)

2023-08-03 13:31:17 -07:00