Embedded HTTP server: Difference between revisions

Revision as of 05:10, 13 November 2007

Revision as of 10:13, 13 November 2007

Line 14:

== Typical requirements ==

Natural limitations of the platforms where an embedded HTTP server runs contribute to the list of the functional requirements of the embedded, or more precise, embeddable HTTP server. Some of these requirements in random order

* "Small" [[RAM]] and [[Read-only memory|ROM]] foot print. The exact number depends on the system, but in many cases anything above singleover digitsseveral MBmegabytes is not embeddable.

* Low [[CPU]] consumption.

* Cross compilation support for multiple CPU +and OSoperating system combinations.

* Easy integration with existing application, including static link with the OSoperating system and application.

* C implementation (compare with C++/Java/C#).

* Easy integration with existing application, including static link with the OS and application.

* Serving pages from the RAM if there is no file system.

* Modularity.

* Single thread and multi-thread support.

For every specific project requirements can vary significantly. For example, ROM and RAM footprints can be very serious constrainconstraint and limit the choices of the system designer. [[C++]] or [[Java Virtual Machine|JVM]] availability for the CPU/system can be another constrainconstraint. Frequently performance is an issue, because typical embedded system runs multiple simultaneous tasks and WEBa HTTP server is only one of them and usually is usually a low priority task.

== Open source servers ==