Criteria for selecting software for embedded device

Posted by Suresh Kumar on Stack Overflow See other posts from Stack Overflow or by Suresh Kumar
Published on 2010-06-02T04:22:15Z Indexed on 2010/06/02 4:23 UTC
Read the original article Hit count: 273

We are currently evaluating Web servers for an embedded device. We have laid down the evaluation criteria for things like HTTP version, Security, Compression etc.

On the embeddable side, we have identified the following criteria:

  1. Memory footprint
  2. Memory management (support for plugging in a custom memory manager)
  3. CPU usage
  4. Thread usage (support for thread pool)
  5. Portability

What I want inputs on is:

  1. Are there any other criteria that an embeddable software should meet?
  2. What exactly does it mean when someone says that a software is designed for embeddable use?

We currently have zeroed in on two Web servers:

  1. AppWeb
  2. Lighttpd (lighty)

Feature wise, both the above Web servers seem to be on par. However, it is claimed that AppWeb is designed for embedded use while Lighttpd is not. To choose between the above two Web servers, what criteria should I be looking at?

© Stack Overflow or respective owner

Related posts about web-development

Related posts about embedded