Commit 7cefb56e by olly Committed by Oliver Woodman

Update comment to indicate correct int value of "FLAG_ALLOW_CACHE_FRAGMENTATION"…

Update comment to indicate correct int value of "FLAG_ALLOW_CACHE_FRAGMENTATION" in ExoPlayer2 upstream DataSpec

Currently the value of FLAG_ALLOW_CACHE_FRAGMENTATION is defined as "1 << 4" but commented as "8". Either the value of FLAG_ALLOW_CACHE_FRAGMENTATION should be "1 << 3", or the comment should be 16. Here I am modifying the comment since it does not affect any current behavior.

PiperOrigin-RevId: 265011839
parent 886fe910
...@@ -68,7 +68,7 @@ public final class DataSpec { ...@@ -68,7 +68,7 @@ public final class DataSpec {
* setting this flag may also enable more concurrent access to the data (e.g. reading one fragment * setting this flag may also enable more concurrent access to the data (e.g. reading one fragment
* whilst writing another). * whilst writing another).
*/ */
public static final int FLAG_ALLOW_CACHE_FRAGMENTATION = 1 << 4; // 8 public static final int FLAG_ALLOW_CACHE_FRAGMENTATION = 1 << 4; // 16
/** /**
* The set of HTTP methods that are supported by ExoPlayer {@link HttpDataSource}s. One of {@link * The set of HTTP methods that are supported by ExoPlayer {@link HttpDataSource}s. One of {@link
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or sign in to comment