From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: "Tanous\, Ed" <ed.tanous@intel.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Request for comments: C++ embedded webserver
Date: Wed, 20 Dec 2017 10:30:40 +1100 [thread overview]
Message-ID: <87zi6ewb1b.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <7E9441B1E5EFFD4681F54958E82169932F4B1A4D@ORSMSX114.amr.corp.intel.com>
"Tanous, Ed" <ed.tanous@intel.com> writes:
> I'm looking for comments on a code review that's been outstanding.
> One of the large pushes we've made is to attempt to make the web
> server more efficient, and add capabilities that comprehend long term
> needs of OpenBmc. One key that wasn't made clear in the commit
> message is that it includes the basic redfish implementation that (we
> hope) should be extensible to the full redfish specification in the
> short term future.
>
> https://gerrit.openbmc-project.xyz/#/c/7786/
>
> We would very much appreciate comments to see if we can move this
> forward.
One question, it seems like you rolled your own http server, any reason
to do that rather than re-use what's in libevent or similar such
library?
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2017-12-19 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 4:07 Request for comments: C++ embedded webserver Tanous, Ed
2017-12-19 23:30 ` Stewart Smith [this message]
2017-12-20 19:49 ` Michael.E.Brown
2017-12-21 0:16 ` Tanous, Ed
2017-12-21 0:34 ` Benjamin Herrenschmidt
2017-12-21 17:25 ` Michael.E.Brown
2017-12-21 18:47 ` Tanous, Ed
2017-12-21 21:40 ` Michael.E.Brown
2017-12-22 0:32 ` Tanous, Ed
2017-12-22 21:45 ` Michael.E.Brown
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=87zi6ewb1b.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=ed.tanous@intel.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.