[gvfs/gdbus: 9/17] gdbus: Don't handle method invocations in threads



commit 6d49a1be2b436eb1477a7c8b2b725ae71fa8ed2b
Author: Tomas Bzatek <tbzatek redhat com>
Date:   Thu Jun 2 11:46:05 2011 +0200

    gdbus: Don't handle method invocations in threads
    
    Per discussion with David it was suggested this is not so good idea
    as long as most volume monitor operations are called async anyway and
    we would have to hassle with GMainContext.

 monitor/proxy/gvfsproxyvolumemonitordaemon.c |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)
---
diff --git a/monitor/proxy/gvfsproxyvolumemonitordaemon.c b/monitor/proxy/gvfsproxyvolumemonitordaemon.c
index 58ada07..5812150 100644
--- a/monitor/proxy/gvfsproxyvolumemonitordaemon.c
+++ b/monitor/proxy/gvfsproxyvolumemonitordaemon.c
@@ -1913,9 +1913,6 @@ bus_acquired_handler_cb (GDBusConnection *conn,
     return;
 
   monitor_daemon = gvfs_remote_volume_monitor_skeleton_new ();
-
-  g_dbus_interface_skeleton_set_flags (G_DBUS_INTERFACE_SKELETON (monitor_daemon),
-                                       G_DBUS_INTERFACE_SKELETON_FLAGS_HANDLE_METHOD_INVOCATIONS_IN_THREAD);
   
   g_signal_connect (monitor_daemon, "handle-is-supported", G_CALLBACK (handle_is_supported), NULL);
   if (monitor != NULL)



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]