| Top |
| gchar * | base-cache-directory | Read / Write / Construct Only |
| gchar * | base-data-directory | Read / Write / Construct Only |
| gchar * | disk-cache-directory | Read / Write / Construct Only |
| gchar * | dom-cache-directory | Read / Write / Construct Only |
| gchar * | hsts-cache-directory | Read / Write / Construct Only |
| gchar * | indexeddb-directory | Read / Write / Construct Only |
| gboolean | is-ephemeral | Read / Write / Construct Only |
| gchar * | itp-directory | Read / Write / Construct Only |
| gchar * | local-storage-directory | Read / Write / Construct Only |
| gchar * | offline-application-cache-directory | Read / Write / Construct Only |
| gchar * | service-worker-registrations-directory | Read / Write / Construct Only |
| gchar * | websql-directory | Read / Write / Construct Only |
GBoxed ├── WebKitITPFirstParty ╰── WebKitITPThirdParty GObject ╰── WebKitWebsiteDataManager
WebKitWebsiteDataManager allows you to manage the data that websites
can store in the client file system like databases or caches.
You can use WebKitWebsiteDataManager to configure the local directories
where the Website data will be stored, by creating a new manager with
webkit_website_data_manager_new() passing the values you want to set.
You can set all the possible configuration values or only some of them,
a default value will be used automatically for the configuration options
not provided. “base-data-directory” and
“base-cache-directory” are two special properties
that can be used to set a common base directory for all Website data and
caches. It's possible to provide both, a base directory and a specific value,
but in that case, the specific value takes precedence over the base directory.
The newly created WebKitWebsiteDataManager must be passed as a construct property
to a WebKitWebContext, you can use webkit_web_context_new_with_website_data_manager()
to create a new WebKitWebContext with a WebKitWebsiteDataManager.
In case you don't want to set any specific configuration, you don't need to create
a WebKitWebsiteDataManager, the WebKitWebContext will create a WebKitWebsiteDataManager
with the default configuration. To get the WebKitWebsiteDataManager of a WebKitWebContext
you can use webkit_web_context_get_website_data_manager().
A WebKitWebsiteDataManager can also be ephemeral and then all the directories configuration
is not needed because website data will never persist. You can create an ephemeral WebKitWebsiteDataManager
with webkit_website_data_manager_new_ephemeral(). Then you can pass an ephemeral WebKitWebsiteDataManager to
a WebKitWebContext to make it ephemeral or use webkit_web_context_new_ephemeral() and the WebKitWebsiteDataManager
will be automatically created by the WebKitWebContext.
WebKitWebsiteDataManager can also be used to fetch websites data, remove data stored by particular websites, or clear data for all websites modified since a given period of time.
WebKitWebsiteDataManager * webkit_website_data_manager_new (const gchar *first_option_name,...);
Creates a new WebKitWebsiteDataManager with the given options. It must be passed as construction parameter of a WebKitWebContext.
first_option_name |
name of the first option to set |
|
... |
value of first option, followed by more options, |
Since: 2.10
WebKitWebsiteDataManager *
webkit_website_data_manager_new_ephemeral
(void);
Creates an ephemeral WebKitWebsiteDataManager. See “is-ephemeral” for more details.
Since: 2.16
gboolean
webkit_website_data_manager_is_ephemeral
(WebKitWebsiteDataManager *manager);
Get whether a WebKitWebsiteDataManager is ephemeral. See “is-ephemeral” for more details.
Since: 2.16
const gchar *
webkit_website_data_manager_get_base_data_directory
(WebKitWebsiteDataManager *manager);
Get the “base-data-directory” property.