On Di, 05.03.19 20:46, Stanislav Angelovič (angelovi...@gmail.com) wrote:
> > To do that, allocate a single mutex of some form covering the sd_bus
> > object and all sd_bus_message associated with it. You need to take the
> > lock when you enter any sd_bus_xyz call, and release it after. To
> >
Hi Lennart,
Thanks a lot for your elaborate reply. See inline replies...
On Tue, Mar 5, 2019 at 11:27 AM Lennart Poettering
wrote:
>
> On Mo, 04.03.19 21:56, Stanislav Angelovič (angelovi...@gmail.com) wrote:
>
>
> sd-bus doesn't natively care for threads. However it's written in kind
> of a
On Mo, 04.03.19 21:56, Stanislav Angelovič (angelovi...@gmail.com) wrote:
> Hi sd-bus-ers!
heya,
> Quick question: How can I process a method call on service side in a
> different thread, without creating race condition?
sd-bus doesn't natively care for threads. However it's written in kind
of
Hi Stanislav,
On Mon, Mar 4, 2019 at 9:56 PM Stanislav Angelovič
wrote:
>
> Hi sd-bus-ers!
>
> Quick question: How can I process a method call on service side in a
> different thread, without creating race condition?
>
> Longer version:
>
> In sdbus-c++, we are working on server-side
Hi sd-bus-ers!
Quick question: How can I process a method call on service side in a
different thread, without creating race condition?
Longer version:
In sdbus-c++, we are working on server-side asynchronous method call
support.
In sd-bus, a service handles D-Bus method calls via
