From: "Frank Ch. Eigler" <fche@redhat.com>
To: Ben Birch <bbirch@aconex.com>
Cc: Paul Smith <psmith@aconex.com>,
pcp@oss.sgi.com, systemtap@sourceware.org
Subject: Re: [pcp] sketch of possible web pmapi
Date: Fri, 25 Mar 2011 01:26:00 -0000 [thread overview]
Message-ID: <20110325012635.GG4401@redhat.com> (raw)
In-Reply-To: <1593492084.6281.1300947065694.JavaMail.root@acxmail-au2.aconex.com>
Hi -
On Thu, Mar 24, 2011 at 05:11:05PM +1100, Ben Birch wrote:
> [...] For something like the pmapi, really a RESTful interface is
> the way to go. If you accept this, you really don't want a RESTful
> api serving xslt [...] Regarding js development: most front end
> engineer are going to be looking for a json api [...]
OK guys, thanks, I'm convinced. I'll start hacking together a
JSON-emitting widget.
- FChE
next prev parent reply other threads:[~2011-03-25 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 17:54 Frank Ch. Eigler
2011-03-22 23:03 ` [pcp] " Paul Smith
2011-03-23 3:58 ` Frank Ch. Eigler
2011-03-23 4:28 ` Paul Smith
2011-03-24 2:09 ` Frank Ch. Eigler
2011-03-24 2:23 ` Paul Smith
2011-03-24 6:11 ` Ben Birch
2011-03-25 1:26 ` Frank Ch. Eigler [this message]
2011-03-23 21:41 ` Nathan Scott
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=20110325012635.GG4401@redhat.com \
--to=fche@redhat.com \
--cc=bbirch@aconex.com \
--cc=pcp@oss.sgi.com \
--cc=psmith@aconex.com \
--cc=systemtap@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).