[ltt-dev] UST communication library

David Goulet david.goulet at polymtl.ca
Wed Jun 15 11:13:51 EDT 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 11-06-15 11:06 AM, Yannick Brosseau wrote:
> On 2011-06-14 17:26, David Goulet wrote:
>> Hi everyone,
>>
>> We are in the process of moving out the UST control library out to lttng-tools
>> (thus soon deprecating ustctl and usttrace from the UST git tree). However,
>> there is a common part which is the communication library (libustcomm) where
>> every command to the tracer and responses are done through a Unix socket using
>> that specific libs (that contains key functions to pack/unpack data).
>>
>> So the problem is where this lib should go? Here are the possibilities I've
>> discussed with Mathieu:
>>
> 
> 7) Define a communication protocol and implement it on both side. That
> way, you have to library to depends on.
> 

This is a re-write of the actual code (will be the third time), code duplication
across two git tree and handling data function will be the same both sides since
it's a bidirectional communication. I really think it's not the best way to do
this.

For this use case where two program needs to communicate together, we need a
third part communication library. So single point of failure, single point to
maintain and no dependency between packages, only the lib, it's a trade off.

Thanks
David

> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJN+MwvAAoJEELoaioR9I02kEYIAKaPzG994seeNnb/MyZUYZfY
seH1g1Lgtzq2qTF0sglq9alwOfD1KnqvPPr+YtkkAKGaN1A+hHO1NxDsn9ZdBBgu
5upkbLuASGd5ZezdUvYSMzYDxyY1WJgUcT/1vkU1BBFaaEFq9rkWHh11LMgBaaIC
FkSy1xSm8WV/BiJ6IGjtiCcUoDeXxruKjp6rTUf9NYo+MMDTp8xf3BKNSmGSdK6S
zyrJBxDZZsbQHd/rcf/6xZtP6sHey0VoiQDB8PlcFA6kBjkMojdu6fPzXDkAAdv5
18kKbGdyY107aLr7KxtYp+9NIXfDGOpKKCu4HqSPmxQsJBgPx+sar/4eF3tD3Kg=
=99lw
-----END PGP SIGNATURE-----




More information about the lttng-dev mailing list