From c8f39fe14d08caa83404a284fcdcd157aa6fa3e9 Mon Sep 17 00:00:00 2001
From: tonihei <tonihei@google.com>
Date: Thu, 1 Feb 2018 04:52:51 -0800
Subject: [PATCH] Update ExoPlayer doc to specifically discourage parallel
 access instead of allowing it.

Even if a developer synchronizes every method, thread safety is still not guaranteed
because the internal callback methods can't be synced from outside.

Issue:#3773

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=184122072
---
 .../main/java/com/google/android/exoplayer2/ExoPlayer.java   | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java b/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java
index a9980f9803..c13fd6cacd 100644
--- a/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java
+++ b/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java
@@ -91,10 +91,9 @@ import com.google.android.exoplayer2.video.MediaCodecVideoRenderer;
  * model">
  *
  * <ul>
- *   <li>It is recommended that ExoPlayer instances are created and accessed from a single
+ *   <li>It is strongly recommended that ExoPlayer instances are created and accessed from a single
  *       application thread. The application's main thread is ideal. Accessing an instance from
- *       multiple threads is discouraged, however if an application does wish to do this then it may
- *       do so provided that it ensures accesses are synchronized.
+ *       multiple threads is discouraged as it may cause synchronization problems.
  *   <li>Registered listeners are called on the thread that created the ExoPlayer instance, unless
  *       the thread that created the ExoPlayer instance does not have a {@link Looper}. In that
  *       case, registered listeners will be called on the application's main thread.