their synchronous counterparts
More in-depth tests have shown that synchronous connection flushing
produces more predictable results under heavy load. Moreover, it seems
to be the only way to ensure stable and predictable execution flow,
where under heavy load the server can become starved even for a few
seconds.
Change-Id: Ia99618b83a3b9d86fd132554583e6d3250b099f9
else
start = 0;
- //GError *error = NULL;
g_dbus_connection_call(conn,
name,
path,
NULL,
NULL,
NULL);
- /*if(error != NULL) {
- g_printerr("Error=%s\n", error->message);
- g_error_free (error);
- }*/
- g_dbus_connection_flush(conn,
- NULL, /* GCancellable */
- NULL, /* GAsyncReadyCallback */
- NULL); /* user_data */
+ GError *error = NULL;
+ g_dbus_connection_flush_sync(conn,
+ NULL,
+ &error);
+ if (error != NULL) {
+ g_printerr("Error=%s\n", error->message);
+ g_error_free (error);
+ }
if(is_lt) {
if(size <= ONE_PAGE_SIZE)
usleep(5000);
NULL,
NULL,
NULL);
- g_dbus_connection_flush(connection,
- NULL, /* GCancellable */
- NULL, /* GAsyncReadyCallback */
- NULL); /* user_data */
+ GError *error = NULL;
+ g_dbus_connection_flush_sync(connection,
+ NULL,
+ &error);
+ if (error != NULL) {
+ g_printerr("Error=%s\n", error->message);
+ g_error_free (error);
+ }
if (is_lt) {
if (size <= ONE_PAGE_SIZE)
usleep(5000);