olly 3fcc14b3c2 OkHttp/Rtmp extensions: Remove dependency on core
They only require common. This allows their use for non-playback networking
without requiring the user to depend on the whole of core. I will also make
the same change for Cronet, although this needs a little more work.

PiperOrigin-RevId: 353649388
2021-01-25 17:38:36 +00:00
..

ExoPlayer OkHttp extension

The OkHttp extension is an HttpDataSource implementation using Square's OkHttp.

License note

Please note that whilst the code in this repository is licensed under Apache 2.0, using this extension requires depending on OkHttp, which is licensed separately.

Getting the extension

The easiest way to use the extension is to add it as a gradle dependency:

implementation 'com.google.android.exoplayer:extension-okhttp:2.X.X'

where 2.X.X is the version, which must match the version of the ExoPlayer library being used.

Alternatively, you can clone the ExoPlayer repository and depend on the module locally. Instructions for doing this can be found in ExoPlayer's top level README.

Using the extension

ExoPlayer requests data through DataSource instances. These instances are either instantiated and injected from application code, or obtained from instances of DataSource.Factory that are instantiated and injected from application code.

If your application only needs to play http(s) content, using the OkHttp extension is as simple as updating any DataSources and DataSource.Factory instantiations in your application code to use OkHttpDataSource and OkHttpDataSourceFactory respectively. If your application also needs to play non-http(s) content such as local files, use

new DefaultDataSource(
    ...
    new OkHttpDataSource(...) /* baseDataSource argument */);

and

new DefaultDataSourceFactory(
    ...
    new OkHttpDataSourceFactory(...) /* baseDataSourceFactory argument */);

respectively.

  • Javadoc: Classes matching com.google.android.exoplayer2.ext.okhttp.* belong to this module.