Common houses DataSource as an interface for reading data, but most of the concrete implementations are in ExoPlayer. This means that in practice, if an app wants to use a module that reads using DataSource (e.g. extractor), they may be forced to depend on ExoPlayer as well to get a concrete implementation (e.g. FileDataSource). This change moves the DataSource implementations into common to resolve this. PiperOrigin-RevId: 403222081
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| crypto | Loading commit data... | |
| AssetDataSourceContractTest.java | Loading commit data... | |
| AssetDataSourceTest.java | Loading commit data... | |
| BaseDataSourceTest.java | Loading commit data... | |
| ByteArrayDataSourceContractTest.java | Loading commit data... | |
| ByteArrayDataSourceTest.java | Loading commit data... | |
| DataSchemeDataSourceContractTest.java | Loading commit data... | |
| DataSchemeDataSourceTest.java | Loading commit data... | |
| DataSourceExceptionTest.java | Loading commit data... | |
| DataSourceInputStreamTest.java | Loading commit data... | |
| DataSpecTest.java | Loading commit data... | |
| DefaultHttpDataSourceContractTest.java | Loading commit data... | |
| DefaultHttpDataSourceTest.java | Loading commit data... | |
| FileDataSourceContractTest.java | Loading commit data... | |
| HttpUtilTest.java | Loading commit data... | |
| ResolvingDataSourceContractTest.java | Loading commit data... | |
| UdpDataSourceContractTest.java | Loading commit data... |