After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759524 - Example program showing usage of complex GVariant types with GDBus RPC
Example program showing usage of complex GVariant types with GDBus RPC
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gdbus
2.47.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2015-12-16 05:32 UTC by jitendra
Modified: 2018-05-24 18:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch for example program showing usage of complex GVariant types with GDBus RPC. (13.61 KB, text/plain)
2015-12-16 05:32 UTC, jitendra
Details

Description jitendra 2015-12-16 05:32:07 UTC
Created attachment 317471 [details]
Patch for example program showing usage of complex GVariant types with GDBus RPC.

After studying the GIO and GDBus documentation I found that there is very little documentation and no examples showing usage of complex GVariant types with GDBus RPC. So I have created an example program that demonstrates usages of following complex GVariant types with GDBus RPC:-

1. Array of tuples Ex. a(iis)
2. Array of dictionary entries Ex. a{is}
3. More complex GVariant type Ex. a(oa{sv})

Example program operates  in client and server mode. Client creates above types of GVariant data and pass them to server using GDBus sync Method call. Server receives the data in its method handler, extracts the actual data from GVariant and prints them.

Please find attached the patch of example program and consider it for adding in gio/tests/. 

Thanks.
Comment 1 GNOME Infrastructure Team 2018-05-24 18:25:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1118.