Glib学习(29) gdbus 的peer to peer简单例子

怼烎@ 2022-12-27 14:00 236阅读 0赞

Peer2Peer模式:这种模式一般称之为点对点的星型结构,Client与Server之间是直接的Peer2Peer的连接,少了DBus Daemon的中转,因此性能较好。

server结构

  1. //创建loop,不运行
  2. pLoop = g_main_loop_new(NULL, FALSE);
  3. //创建skeleton
  4. pSkeleton = rtplay_gdbus_example_skeleton_new();
  5. //获得guid
  6. _guid = g_dbus_generate_guid();
  7. //创建一个新的D-Bus服务器,该服务器侦听有效address中的第一个地址。
  8. _server = g_dbus_server_new_sync("unix:abstract=gdbus_server", G_DBUS_SERVER_FLAGS_AUTHENTICATION_ALLOW_ANONYMOUS,
  9. _guid, NULL, NULL, &_error);
  10. //注册new-connection,在客户端链接时被调用
  11. g_signal_connect(_server, "new-connection", G_CALLBACK(on_new_connection), NULL);
  12. //启动server。
  13. g_dbus_server_start(_server);
  14. //运行loop
  15. g_main_loop_run(pLoop);

on_new_connection函数

  1. //获得_iface
  2. _iface = RTPLAY_GDBUS_EXAMPLE_GET_IFACE(pSkeleton);
  3. //注册方法,当客户端调用时会被执行
  4. _iface->handle_my_method1 = My_Method1;
  5. //导出interface,获得connection。
  6. g_dbus_interface_skeleton_export(G_DBUS_INTERFACE_SKELETON(pSkeleton), connection, RTPLAY_GDBUS_EXAMPLE_OBJECT_PATH,
  7. &_error);
  8. //注册closed,在客户端断开时被调用
  9. g_signal_connect(connection, "closed", G_CALLBACK(on_close_connection), user_data);

client结构

  1. //创建loop,不运行
  2. pLoop = g_main_loop_new(NULL, FALSE);
  3. //同步连接并建立D-Bus客户端连接,以与由地址指定的端点交换D-Bus消息。
  4. _pGdbus_connection = g_dbus_connection_new_for_address_sync(
  5. "unix:abstract=gdbus_server", G_DBUS_CONNECTION_FLAGS_AUTHENTICATION_CLIENT, NULL, NULL, &_pError);
  6. //创建proxy,链接信号使用
  7. pProxy = rtplay_gdbus_example_proxy_new_sync(_pGdbus_connection, G_DBUS_PROXY_FLAGS_NONE, NULL,
  8. RTPLAY_GDBUS_EXAMPLE_OBJECT_PATH, NULL, &_pError);
  9. //信号链接
  10. g_signal_connect(pProxy, "my-signal1", G_CALLBACK(My_Signal_1_Handler), NULL);
  11. //运行loop
  12. g_main_loop_run(pLoop);

安装教程

  1. mkdir build
  2. cd build/
  3. cmake ..
  4. make

运行结果

  1. $ ./server/SvrExample
  2. InitDBusCommunicationServer: Server started.
  3. New thread created: Success
  4. run call in the server.
  5. Emit_My_Signal1() is called.
  6. Emit_My_Signal1() is called.
  7. Emit_My_Signal2() is called.
  8. Emit_My_Signal1() is called.
  9. Emit_My_Signal1() is called.
  10. Emit_My_Signal2() is called.
  11. Emit_My_Signal1() is called.
  12. Emit_My_Signal1() is called.
  13. Emit_My_Signal2() is called.
  14. Emit_My_Signal1() is called.
  15. Emit_My_Signal1() is called.
  16. Emit_My_Signal2() is called.
  17. A new connection [ 0x7f0c24004040 ] was created
  18. Emit_My_Signal1() is called.
  19. Server MyMethod1 call. Parameter: method1 synchronize call..
  20. Server MyMethod1 call. Parameter: method1 asynchronize call..
  21. Server MyMethod2 call. Parameter: in_arg1 = 12 , in_arg2 = 34.
  22. Server MyMethod2 call. Parameter: in_arg1 = 10 , in_arg2 = 21.
  23. Emit_My_Signal1() is called.
  24. Emit_My_Signal2() is called.
  25. Emit_My_Signal1() is called.
  26. Emit_My_Signal2() is called.
  27. Emit_My_Signal1() is called.
  28. Emit_My_Signal1() is called.
  29. Emit_My_Signal1() is called.
  30. Emit_My_Signal2() is called.
  31. The (null) connection [ 0x7f0c24004040 ] was closed!
  32. Emit_My_Signal1() is called.
  33. $ ./example/CltExample
  34. InitDBusCommunication: Client started.
  35. New thread created: Success
  36. run call in the client.
  37. Signal_1_Callback: String value: Server Signal1(13).
  38. client myMethod_1 call, in_arg = method1 synchronize call. out_arg = Server My_Method1 to output..
  39. client myMethodAsync_1 call, in_arg = method1 asynchronize call..
  40. client MethodCallback_1 call.
  41. Method1Callback: return value: Server My_Method1 to output..
  42. client myMethod_2 call, in_arg1 = 12, in_arg2 = 34, out_arg1 = Server MyMethod2 to output., out_arg2 = 46.
  43. client myMethodAsync_2 call, in_arg1 = 10, in_arg2 = 21.
  44. client MethodCallback_2 call.
  45. Method2Callback: return value: (Server MyMethod2 to output., 31).
  46. Signal_1_Callback: String value: Server Signal1(14).
  47. Signal_2_Callback: Int value: 15, String value: Server Signal2
  48. Signal_1_Callback: String value: Server Signal1(16).
  49. Signal_2_Callback: Int value: 17, String value: Server Signal2
  50. Signal_1_Callback: String value: Server Signal1(18).
  51. Signal_1_Callback: String value: Server Signal1(19).
  52. Signal_1_Callback: String value: Server Signal1(20).
  53. Signal_2_Callback: Int value: 21, String value: Server Signal2

源码下载地址:https://gitee.com/RTplay/gdbus-p2p-demo

其中gdbus-example-peer.c是官方的示例代码,这个逻辑非常全,如果想减少不必要的调试可以参考这个文件。

发表评论

表情:
评论列表 (有 0 条评论,236人围观)

还没有评论,来说两句吧...

相关阅读

    相关 How to verify the peer socket is dead?

    对于`TCP/IP`网络编程而言,我们在读写数据时,当然希望获知对端是否还活着!量子纠缠态当然很是理想,但是现实网络世界中,两个不可见端点互相通讯,确定对方还活着的方法就是不断

    相关 Peer To Peer——对等网络

           今年的考试,大问题没怎么出现。就是考英语第二天的下午,发生网络堵塞的现象,不影响大局,但是事出有因,我们还是需要看看是什么影响到了考生抽题。最后查了一圈,发现其他