From 5b08df001a5c04ab5987f8f635fff4ab8c4f11b3 Mon Sep 17 00:00:00 2001 From: ibaker Date: Thu, 24 Mar 2022 15:13:09 +0000 Subject: [PATCH] Remove references to deprecated DefaultDataSourceFactory from dev guide #minor-release PiperOrigin-RevId: 436997521 --- docs/customization.md | 2 +- docs/network-stacks.md | 6 +++--- extensions/cronet/README.md | 3 ++- extensions/rtmp/README.md | 2 +- 4 files changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/customization.md b/docs/customization.md index 0023682862..33159e4ff5 100644 --- a/docs/customization.md +++ b/docs/customization.md @@ -59,7 +59,7 @@ DataSource.Factory httpDataSourceFactory = DefaultDataSource.Factory dataSourceFactory = new DefaultDataSource.Factory(context, httpDataSourceFactory); -// Inject the DefaultDataSourceFactory when creating the player. +// Inject the DefaultDataSource.Factory when creating the player. ExoPlayer player = new ExoPlayer.Builder(context) .setMediaSourceFactory(new DefaultMediaSourceFactory(dataSourceFactory)) diff --git a/docs/network-stacks.md b/docs/network-stacks.md index 5b791bfaca..cdacdce154 100644 --- a/docs/network-stacks.md +++ b/docs/network-stacks.md @@ -22,14 +22,14 @@ that corresponds to the network stack you wish to use. If your application also needs to play non-http(s) content such as local files, use ~~~ -new DefaultDataSourceFactory( +new DefaultDataSource.Factory( ... /* baseDataSourceFactory= */ new PreferredHttpDataSource.Factory(...)); ~~~ {: .language-java} where `PreferredHttpDataSource.Factory` is the factory corresponding to your -preferred network stack. The `DefaultDataSourceFactory` layer adds in support +preferred network stack. The `DefaultDataSource.Factory` layer adds in support for non-http(s) sources such as local files. The example below shows how to build an `ExoPlayer` that will use the Cronet @@ -48,7 +48,7 @@ DefaultDataSource.Factory dataSourceFactory = context, /* baseDataSourceFactory= */ cronetDataSourceFactory); -// Inject the DefaultDataSourceFactory when creating the player. +// Inject the DefaultDataSource.Factory when creating the player. ExoPlayer player = new ExoPlayer.Builder(context) .setMediaSourceFactory(new DefaultMediaSourceFactory(dataSourceFactory)) diff --git a/extensions/cronet/README.md b/extensions/cronet/README.md index fc22a77d33..ff8de92687 100644 --- a/extensions/cronet/README.md +++ b/extensions/cronet/README.md @@ -38,8 +38,9 @@ If your application only needs to play http(s) content, using the Cronet extension is as simple as updating `DataSource.Factory` instantiations in your application code to use `CronetDataSource.Factory`. If your application also needs to play non-http(s) content such as local files, use: + ``` -new DefaultDataSourceFactory( +new DefaultDataSource.Factory( ... /* baseDataSourceFactory= */ new CronetDataSource.Factory(...) ); ``` diff --git a/extensions/rtmp/README.md b/extensions/rtmp/README.md index f825b03367..0bc2bb73d6 100644 --- a/extensions/rtmp/README.md +++ b/extensions/rtmp/README.md @@ -39,7 +39,7 @@ injected from application code. `DefaultDataSource` will automatically use the RTMP extension whenever it's available. Hence if your application is using `DefaultDataSource` or -`DefaultDataSourceFactory`, adding support for RTMP streams is as simple as +`DefaultDataSource.Factory`, adding support for RTMP streams is as simple as adding a dependency to the RTMP extension as described above. No changes to your application code are required. Alternatively, if you know that your application doesn't need to handle any other protocols, you can update any