java.lang.Object | |
↳ | android.webkit.CookieSyncManager |
This class was deprecated
in API level 21.
The WebView now automatically syncs cookies as necessary.
You no longer need to create or use the CookieSyncManager.
To manually force a sync you can use the CookieManager
method flush()
which is a synchronous
replacement for sync()
.
The CookieSyncManager is used to synchronize the browser cookie store between RAM and permanent storage. To get the best performance, browser cookies are saved in RAM. A separate thread saves the cookies between, driven by a timer.
To use the CookieSyncManager, the host application has to call the following when the application starts:
CookieSyncManager.createInstance(context)
To set up for sync, the host application has to call
CookieSyncManager.getInstance().startSync()
in Activity.onResume(), and call
CookieSyncManager.getInstance().stopSync()
in Activity.onPause().
To get instant sync instead of waiting for the timer to trigger, the host can call
CookieSyncManager.getInstance().sync()
The sync interval is 5 minutes, so you will want to force syncs
manually anyway, for instance in onPageFinished(WebView, String)
. Note that even sync() happens
asynchronously, so don't do it just as your activity is shutting
down.
Constants | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
String | LOGTAG |
Fields | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
mDataBase | |||||||||||
mHandler |
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Create a singleton CookieSyncManager within a context
| |||||||||||
Singleton access to a
CookieSyncManager .
| |||||||||||
This method is deprecated.
Calling resetSync is no longer necessary as the WebView automatically
syncs cookies.
| |||||||||||
Starts executing the active part of the class' code.
| |||||||||||
This method is deprecated.
Calling startSync is no longer necessary as the WebView automatically
syncs cookies.
| |||||||||||
This method is deprecated.
Calling stopSync is no longer useful as the WebView
automatically syncs cookies.
| |||||||||||
This method is deprecated.
Use
flush() instead.
|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Creates and returns a copy of this
Object .
| |||||||||||
This method was deprecated
in API level 21.
Use
flush() instead.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
| |||||||||||
From interface
java.lang.Runnable
|
Create a singleton CookieSyncManager within a context
Singleton access to a CookieSyncManager
. An
IllegalStateException will be thrown if
createInstance(Context)
is not called before.
This method is deprecated.
Calling resetSync is no longer necessary as the WebView automatically
syncs cookies.
resetSync() resets sync manager's timer.
Starts executing the active part of the class' code. This method is
called when a thread is started that has been created with a class which
implements Runnable
.
This method is deprecated.
Calling startSync is no longer necessary as the WebView automatically
syncs cookies.
startSync() requests sync manager to start sync.
This method is deprecated.
Calling stopSync is no longer useful as the WebView
automatically syncs cookies.
stopSync() requests sync manager to stop sync. remove any SYNC_MESSAGE in the queue to break the sync loop
Creates and returns a copy of this Object
. The default
implementation returns a so-called "shallow" copy: It creates a new
instance of the same class and then copies the field values (including
object references) from this instance to the new instance. A "deep" copy,
in contrast, would also recursively clone nested objects. A subclass that
needs to implement this kind of cloning should call super.clone()
to create the new instance and then create deep copies of the nested,
mutable objects.
CloneNotSupportedException |
---|