public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Laurie Gellatly <laurie.gellatly@netic.com>
To: Bernd Schuster <schuster_bernd@gmx.net>
Cc: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] suitable web server for ecos
Date: Wed, 12 Dec 2012 23:22:00 -0000	[thread overview]
Message-ID: <FCE5F206-C6AF-4265-A6B7-A2E1EF6A1228@netic.com> (raw)
In-Reply-To: <20121212211251.281700@gmx.net>

Hi Bernd,
For my project I used an earlier version of mongoose. I've shared it with other members of the group. It has desirable features above httpd.

Had the same issues with goahead.

...Laurie:{)


On 13/12/2012, at 8:12 AM, "Bernd Schuster" <schuster_bernd@gmx.net> wrote:

> Hi, 
> 
> I`m doing a ethernet switch project with eCos and a 400MHZ MIPS Prozessor. For my application I`ll need a web server to configurate the fixture. At the moment I`m using the httpd web server which is already included in the ecos enviroment. It`s working but it takes a long time at startup to be able to open the first webpage. I`m not sure if the httpd source code is responsible for this delay or any other part of the ecos. 
> 
> In the reference manual of the ecos o/s, I read that httpd is maybe not the best solution (http://ecos.sourceware.org/docs-2.0/ref/net-httpd-chapter.html). I`v also heard about the Goahead webserver, but the fact that we`ve to include the logo at the startpage makes this web server unusable for this project. But there`s another web server, called "appweb" which should be fast and also small... but I`m not quite sure if it is suitable for a ecos system because it looks like equal to apache server. 
> 
> First of all I`ll need a very fast web server, which supports HTTPS and IPv6, GET and POST requests. As content, I`ll create and send xml and xsl files instead of html files. Therefore it would be great if it web server has a fast xml parser. 
> 
> At the moment I found the following web servers: httpd, goahead, appweb and mongoose. Do you know any further web servers I should take into account? And which web server will you suggest?
> 
> best regards 
> Bernd
> 
> 
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2012-12-12 23:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 21:13 Bernd Schuster
2012-12-12 23:22 ` Laurie Gellatly [this message]

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=FCE5F206-C6AF-4265-A6B7-A2E1EF6A1228@netic.com \
    --to=laurie.gellatly@netic.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=schuster_bernd@gmx.net \
    /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).