This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [pcp] suitability of PCP for event tracing

From: Greg Banks <gnb at evostor dot com>
To: "nathans at aconex dot com" <nathans at aconex dot com>
Cc: "Frank Ch. Eigler" <fche at redhat dot com>, "pcp at oss dot sgi dot com" <pcp at oss dot sgi dot com>, "systemtap at sources dot redhat dot com" <systemtap at sources dot redhat dot com>, Mark Goodwin <mgoodwin at redhat dot com>
Date: Thu, 2 Sep 2010 14:10:50 +1000
Subject: Re: [pcp] suitability of PCP for event tracing
References: <1219414988.590221283398911155.JavaMail.root@mail-au.aconex.com>

nathans@aconex.com wrote:

----- "Greg Banks" <gnb@evostor.com> wrote:

[...] create a very simple stateless HTTP-to-PCP protocol bridge daemon [...]


That echo's my thoughts, we should be able to extend pmproxy to do this
too - instead of simply proxying native protocol, it could convert from
XML/JSON client requests on the front end to regular PCP protocol on the
backend (optionally, and only if the client requests come in that way so
existing proxy protocol unchanged).  Then we wouldn't need a new daemon,
etc.

Sure we could do it in pmproxy, but I don't see what it buys us other than not having to start one more daemon in the init script?

--
Greg.

References:
- Re: [pcp] suitability of PCP for event tracing
  - From: nathans

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]