Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: david.goulet@polymtl.ca (David Goulet)
Subject: [ltt-dev] UST communication library
Date: Wed, 15 Jun 2011 11:13:51 -0400	[thread overview]
Message-ID: <4DF8CC2F.9000401@polymtl.ca> (raw)
In-Reply-To: <4DF8CA8C.8040309@gmail.com>

-----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-----




  reply	other threads:[~2011-06-15 15:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 21:26 David Goulet
2011-06-15  5:23 ` Alexandre Montplaisir
2011-06-15  8:09   ` Nils Carlson
2011-06-15 14:57   ` David Goulet
2011-06-15 15:01     ` Yannick Brosseau
2011-06-15 15:16       ` David Goulet
2011-06-15 15:21         ` Yannick Brosseau
2011-06-15 15:24           ` David Goulet
2011-06-15 15:26             ` Yannick Brosseau
2011-06-15 15:41               ` Mathieu Desnoyers
2011-06-15 18:51         ` Alexandre Montplaisir
2011-06-15 15:06 ` Yannick Brosseau
2011-06-15 15:13   ` David Goulet [this message]
2011-06-15 15:16     ` Yannick Brosseau
2011-06-15 15:32     ` Mathieu Desnoyers
     [not found]     ` <BLU0-SMTP5372DAF7E219ACFC9DE44C966B0@phx.gbl>
2011-06-15 15:55       ` Yannick Brosseau
2011-06-15 17:16         ` Mathieu Desnoyers
2011-06-15 19:11           ` Alexandre Montplaisir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DF8CC2F.9000401@polymtl.ca \
    --to=david.goulet@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox