Class WebDAVCollectionBackend

Whenever the source_property is changed the target_property is updated using the same value. For instance:

  g_object_bind_property (action, "active", widget, "sensitive", 0);

Will result in the "sensitive" property of the widget #GObject instance to be updated with the same value of the "active" property of the action #GObject instance.

If flags contains %G_BINDING_BIDIRECTIONAL then the binding will be mutual: if target_property on target changes then the source_property on source will be updated as well.

The binding will automatically be removed when either the source or the target instances are finalized. To remove the binding without affecting the source and the target you can just call g_object_unref() on the returned #GBinding instance.

Removing the binding by calling g_object_unref() on it must only be done if the binding, source and target are only used from a single thread and it is clear that both source and target outlive the binding. Especially it is not safe to rely on this if the binding, source or target can be finalized from different threads. Keep another reference to the binding and use g_binding_unbind() instead to be on the safe side.

A #GObject can have multiple bindings.

This function is the language bindings friendly version of g_object_bind_property_full(), using #GClosures instead of function pointers.

The backend is then expected to compare the returned list with a current list of resources from a remote server, create new #ESource instances as needed with e_collection_backend_new_child(), discard unneeded #ESource instances with e_source_remove(), and export the remaining instances with e_source_registry_server_add_source().

The sources returned in the list are referenced for thread-safety. They must each be unreferenced with g_object_unref() when finished with them. Free the returned #GList itself with g_list_free().

An easy way to free the list properly in one step is as follows:

|[ g_list_free_full (list, g_object_unref);

It is the implementor's responsibility to examine source and determine what the equivalent server-side resource would be. If this cannot be determined without ambiguity, the function must return an error.

After the server-side resource is successfully created, the implementor must also add an #ESource to backend's #ECollectionBackend:server. This can either be done immediately or in response to some "resource created" notification from the server. The added #ESource can be source itself or a different #ESource instance that describes the new resource.

When the operation is finished, callback will be called. You can then call e_collection_backend_create_resource_finish() to get the result of the operation.

If an error occurred, the function will set error and return %FALSE.

It is the implementor's responsibility to examine source and determine what the equivalent server-side resource would be. If this cannot be determined without ambiguity, the function must return an error.

After the server-side resource is successfully created, the implementor must also add an #ESource to backend's #ECollectionBackend:server. This can either be done immediately or in response to some "resource created" notification from the server. The added #ESource can be source itself or a different #ESource instance that describes the new resource.

If an error occurs, the function will set error and return %FALSE.

When the operation is finished, callback will be called. You can then call e_backend_credentials_required_finish() to get the result of the operation.

If an error occurs, the function sets error and returns %FALSE.

The provided credentials are received through #EBackendClass.authenticate_sync() method asynchronously.

If an error occurs, the function sets error and returns %FALSE.

After the server-side resource is successfully deleted, the implementor must also remove source from the backend's #ECollectionBackend:server. This can either be done immediately or in response to some "resource deleted" notification from the server.

When the operation is finished, callback will be called. You can then call e_collection_backend_delete_resource_finish() to get the result of the operation.

If an error occurred, the function will set error and return %FALSE.

After the server-side resource is successfully deleted, the implementor must also remove source from the backend's #ECollectionBackend:server. This can either be done immediately or in response to some "resource deleted" notification from the server.

If an error occurs, the function will set error and return %FALSE.

The returned string should be freed with g_free() when no longer needed.

This is necessary for accessors that modify multiple properties to prevent premature notification while the object is still being modified.

The cache directory is meant to store key files for backend-created data sources. See also: e_server_side_source_set_write_directory()

If the #EBackend:connectable property is non-%NULL, the backend will automatically determine whether the network service should be reachable, and hence whether the backend is #EBackend:online. But subclasses may override the online state if, for example, a connection attempt fails.

The value can be:

• an empty #GValue initialized by %G_VALUE_INIT, which will be automatically initialized with the expected type of the property (since GLib 2.60)
• a #GValue initialized with the expected type of the property
• a #GValue initialized with a type to which the expected type of the property can be transformed

In general, a copy is made of the property contents and the caller is responsible for freeing the memory by calling g_value_unset().

Note that g_object_get_property() is really intended for language bindings, g_object_get() is much more convenient for C programming.

The returned instance is owned by the backend.

The sources returned in the list are referenced for thread-safety. They must each be unreferenced with g_object_unref() when finished with them. Free the returned #GList itself with g_list_free().

An easy way to free the list properly in one step is as follows:

|[ g_list_free_full (list, g_object_unref);

The sources returned in the list are referenced for thread-safety. They must each be unreferenced with g_object_unref() when finished with them. Free the returned #GList itself with g_list_free().

An easy way to free the list properly in one step is as follows:

|[ g_list_free_full (list, g_object_unref);

The sources returned in the list are referenced for thread-safety. They must each be unreferenced with g_object_unref() when finished with them. Free the returned #GList itself with g_list_free().

An easy way to free the list properly in one step is as follows:

|[ g_list_free_full (list, g_object_unref);

The returned data source should be passed to e_source_registry_server_add_source() to export it over D-Bus.

When possible, eg. when signaling a property change from within the class that registered the property, you should use g_object_notify_by_pspec() instead.

Note that emission of the notify signal may be blocked with g_object_freeze_notify(). In this case, the signal emissions are queued and will be emitted (in reverse order) when g_object_thaw_notify() is called.

This function omits the property name lookup, hence it is faster than g_object_notify().

One way to avoid using g_object_notify() from within the class that registered the properties, and using g_object_notify_by_pspec() instead, is to store the GParamSpec used with g_object_class_install_property() inside a static array, e.g.:

  enum
  {
    PROP_0,
    PROP_FOO,
    PROP_LAST
  };

  static GParamSpec *properties[PROP_LAST];

  static void
  my_object_class_init (MyObjectClass *klass)
  {
    properties[PROP_FOO] = g_param_spec_int ("foo", "Foo", "The foo",
                                             0, 100,
                                             50,
                                             G_PARAM_READWRITE);
    g_object_class_install_property (gobject_class,
                                     PROP_FOO,
                                     properties[PROP_FOO]);
  }

and then notify a change on the "foo" property with:

  g_object_notify_by_pspec (self, properties[PROP_FOO]);

Since GLib 2.56, if GLIB_VERSION_MAX_ALLOWED is 2.56 or greater, the type of object will be propagated to the return type (using the GCC typeof() extension), so any casting the caller needs to do on the return type must be explicit.

The initial value of the #EBackend:connectable property is derived from the #ESourceAuthentication extension of the backend's #EBackend:source property, if the extension is present.

The returned #GSocketConnectable is referenced for thread-safety and must be unreferenced with g_object_unref() when finished with it.

The returned #GMainContext is referenced for thread-safety and must be unreferenced with g_main_context_unref() when finished with it.

The returned #GProxyResolver is referenced for thread-safety and must be unreferenced with g_object_unref() when finished with it.

The returned #ESourceRegistryServer is referenced for thread-safety. Unreference the #ESourceRegistryServer with g_object_unref() when finished with it.

In other words, if the object is floating, then this call "assumes ownership" of the floating reference, converting it to a normal reference by clearing the floating flag while leaving the reference count unchanged. If the object is not floating, then this call adds a new normal reference increasing the reference count by one.

Since GLib 2.56, the type of object will be propagated to the return type under the same conditions as for g_object_ref().

This function should only be called from object system implementations.

The initial value of the #EBackend:connectable property is derived from the #ESourceAuthentication extension of the backend's #EBackend:source property, if the extension is present.

If the object already had an association with that name, the old association will be destroyed.

Internally, the key is converted to a #GQuark using g_quark_from_string(). This means a copy of key is kept permanently (even after object has been finalized) — so it is recommended to only use a small, bounded set of values for key in your program, to avoid the #GQuark storage growing unbounded.

If the #EBackend:connectable property is non-%NULL, the backend will automatically determine whether the network service should be reachable, and hence whether the backend is #EBackend:online. But subclasses may override the online state if, for example, a connection attempt fails.

void
object_add_to_user_list (GObject     *object,
                         const gchar *new_string)
{
  // the quark, naming the object data
  GQuark quark_string_list = g_quark_from_static_string ("my-string-list");
  // retrieve the old string list
  GList *list = g_object_steal_qdata (object, quark_string_list);

  // prepend new string
  list = g_list_prepend (list, g_strdup (new_string));
  // this changed 'list', so we need to set it again
  g_object_set_qdata_full (object, quark_string_list, list, free_string_list);
}
static void
free_string_list (gpointer data)
{
  GList *node, *list = data;

  for (node = list; node; node = node->next)
    g_free (node->data);
  g_list_free (list);
}

Using g_object_get_qdata() in the above example, instead of g_object_steal_qdata() would have left the destroy function set, and thus the partial string list would have been freed upon g_object_set_qdata_full().

Duplicate notifications for each property are squashed so that at most one #GObject::notify signal is emitted for each property, in the reverse order in which they have been queued.

It is an error to call this function when the freeze count is zero.

When the operation is finished, callback will be called. You can then call e_backend_trust_prompt_finish() to get the result of the operation.

If the pointer to the #GObject may be reused in future (for example, if it is an instance variable of another object), it is recommended to clear the pointer to %NULL rather than retain a dangling pointer to a potentially invalid #GObject instance. Use g_clear_object() for this.

It is the implementor's responsibility to examine source and determine what the equivalent server-side resource would be. If this cannot be determined without ambiguity, the function must return an error.

After the server-side resource is successfully created, the implementor must also add an #ESource to backend's #ECollectionBackend:server. This can either be done immediately or in response to some "resource created" notification from the server. The added #ESource can be source itself or a different #ESource instance that describes the new resource.

When the operation is finished, callback will be called. You can then call e_collection_backend_create_resource_finish() to get the result of the operation.

If an error occurred, the function will set error and return %FALSE.

It is the implementor's responsibility to examine source and determine what the equivalent server-side resource would be. If this cannot be determined without ambiguity, the function must return an error.

After the server-side resource is successfully created, the implementor must also add an #ESource to backend's #ECollectionBackend:server. This can either be done immediately or in response to some "resource created" notification from the server. The added #ESource can be source itself or a different #ESource instance that describes the new resource.

If an error occurs, the function will set error and return %FALSE.

After the server-side resource is successfully deleted, the implementor must also remove source from the backend's #ECollectionBackend:server. This can either be done immediately or in response to some "resource deleted" notification from the server.

When the operation is finished, callback will be called. You can then call e_collection_backend_delete_resource_finish() to get the result of the operation.

If an error occurred, the function will set error and return %FALSE.

After the server-side resource is successfully deleted, the implementor must also remove source from the backend's #ECollectionBackend:server. This can either be done immediately or in response to some "resource deleted" notification from the server.

If an error occurs, the function will set error and return %FALSE.

The returned string should be freed with g_free() when no longer needed.

When possible, eg. when signaling a property change from within the class that registered the property, you should use g_object_notify_by_pspec() instead.

Note that emission of the notify signal may be blocked with g_object_freeze_notify(). In this case, the signal emissions are queued and will be emitted (in reverse order) when g_object_thaw_notify() is called.