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


----- "Frank Ch. Eigler" <fche@redhat.com> wrote:

> Greg Banks <gnb@evostor.com> writes:
> 
> >>> For the web-based frontend issue, yeah, javascript+svg+etc.
> sounds
> >>> most promising, especially if it can be made to speak the native
> wire
> >>> protocol to pmcd.
> 
> Sure; that could be tackled later / orthogonally in principle.  But
> since modern javascript appears to lack low level socket access APIs,
> this may have to be done whether we like it or not.  (Or go Java.)
> ...
> > [...]  Instead I would abandon all attempts at building a time
> > machine, push all the brains out to JS code in the browser, and
> > create a very simple stateless HTTP-to-PCP protocol bridge daemon
> to
> > allow PCP data to be shipped from pmcd to frontend code as either
> > XML or JSON.  Modern browsers have sufficiently fast and functional
> > JS engines that this is now feasible.
> 
> OK, then it looks like we'd have at least a few separate pieces to
> work on:
> ...
> * a PMCD<->XMLRPC bridge

Just as an FYI - I've begun prototyping this.  I have access to a bevy
of web programmers here too, so hopefully can leverage their knowledge
in this space too.  I'll be starting out with my pmproxy approach, but
if that becomes problematic will go the separate daemon route.

I expect we will be running this in our production environments before
too long too, now that its occured to us :) we have immediate users of
this info with a more web/java friendly protocol.

cheers.

-- 
Nathan


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