Hi Rick,
no flames, that's a perfectly legit question. And a great one, I might add.
There's actually a number of options, in ascending complexity, each one
comes with its own advantages/disadvantages.
(1) Use Thrift only for serialization. Write all the data into a memory
buffer or memory stream, then send and receive the bytes by means of the
desired transport medium. That is the easiest way but also the leats
comfortable way, because you will have to take care to ship and receive the
serialized bits.
(2) Write your own transport to integrate the dbus specifics and make the
whole thing easily reusable. Thrift is open in a way where you can
comparingly easy write your own customized transport and integrate it into
the system. All transports in Thrift inherit from or implement a base
TTransport class or interface. This TTransport thing has a few methods, not
too many, that need to be implemented. That should be sufficient to build
some rudimentary serialization/deserialization layer. There are a few
examples under /contrib that may be helpful with this.
(3) Add also a server transport to make it easy to implement servers for
incoming messages. I have some yet unfinished code in my personal Github
fork that implements a Redis transport for netstd which works that way. Some
day I will merge that into master, when I find the time to bring it up to
date and make it ready for a PR.
In the case of (2) or (3) you could consider contribute back and send a PR,
if that makes sense to you.
https://thrift.apache.org/docs/concepts
Have fun,
JensG
-----Ursprüngliche Nachricht-----
From: Rick Tillery
Sent: Wednesday, May 6, 2020 6:56 PM
To: user@thrift.apache.org
Subject: Linux DBus Transport?
I Googled and looked at some of the archives, but I couldn't figure
out how to search them all together, and one month at a time was
taking a long time. So, hopefully I won't get too many flames here
when I ask here:
Is there any implementation available of a DBus transport (for Linux)?
Thank you,
Rick
