Bug 9832

Summary: [PATCH]Providing new dbus-glib APIs for specifying the timeout
Product: dbus Reporter: Nallammai <snallammai>
Component: GLibAssignee: Rob Taylor <rob.taylor>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium Keywords: patch
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: A diff file with the new dbus-glib APIs

Description Nallammai 2007-01-31 20:58:28 UTC
This patch is intended to provide new glib API's that allows the user to specify the timeout parameter for the method calls. 
Currently, in the dbus-glib APIs,the timeout value for synchronous and asynchronous method calls is hard coded as -1(ie.25seconds) which inhibits the user from specifying shorter or longer timeout values.The new APIs take the timeout value as an argument and processes the method calls.
Comment 1 Nallammai 2007-01-31 21:15:01 UTC
Created attachment 8556 [details] [review]
A diff file with the new dbus-glib APIs

The patch contains two new dbus-glib APIs
(i) dbus_g_proxy_call_with_timeout ( DBusGProxy *proxy,
                                     const char *method,
                                     int timeout,
                                     GError **error,
                                     GType first_arg_type,
                                     ...) ;
    This function invokes the method synchronously.

(ii) dbus_g_proxy_begin_call_with_timeout ( DBusGProxy *proxy,
                                            const char *method,
                                            DBusGProxyCallNotify notify,
                                            gpointer user_data,
                                            GDestroyNotify destroy,
                                            int timeout,
                                            GType first_arg_type,
                                            ...) ;
      This function invokes the method asynchronously.
Comment 2 Rob Taylor 2007-02-08 15:53:09 UTC
Thanks Nallammai, these look good. Committed in git head.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.