Embedded HTTP server: Difference between revisions

Revision as of 10:10, 27 November 2010

Latest revision as of 15:25, 5 March 2025

(78 intermediate revisions by 52 users not shown)

Line 1:

{{UnreferencedMore citations needed|date=JuneAugust 20082022}}

[[File:2453 IP video server.jpg|thumb|148x200px|right|Front and back views of a small IP video server (Sensoray 2453S) with audio and composite video inputs served via [[HTTP server]] and other protocols.]]

An '''embedded HTTP server''' is a component of a software system that implements the [[Hypertext Transfer Protocol|HTTP]] protocol. Examples of usage within an application might be:

An '''embedded HTTP server''' is an [[HTTP server]] used in an [[embedded system]].

* To provide a [[thin-client]] interface for a traditional application..

* To provide [[indexing]], [[reporting]], and [[debugging]] tools during the development stage.

* To implement a protocol for the distribution and acquisition of information to be displayed in the regular interface — possibly a [[web service]], and possibly using [[XML]] as the data format.

* To develop a [[web application]]

The HTTP server is usually implemented as a [[software component]] of an [[Application software|application]] (embedded) system that controls and/or monitors a machine with mechanical and/or electrical parts.<ref>{{cite journal |title=Edge Computing Using Embedded Webserver with Mobile Device for Diagnosis and Prediction of Metastasis in Histopathological Images |year=2021 |doi=10.1007/s44196-021-00040-x |last1=Johny |first1=Anil |last2=Madhusoodanan |first2=K. N. |journal=International Journal of Computational Intelligence Systems |volume=14 |s2cid=244923748 |doi-access=free }}</ref>

There are a few advantages to using HTTP to perform the above:

* HTTP is a well studied cross-platform protocol and there are mature implementations freely available.

* HTTP is seldom blocked by firewalls and intranet routers.

* HTTP clients (e.g. [[web browser]]s) are readily available with all modern computers.

* There is a growing tendency of using embedded HTTP servers in applications that parallels the rising trends of home-networking and [[ubiquitous computing]].

The HTTP server implements the [[Hypertext Transfer Protocol|HTTP]] [[Communications protocol|protocol]] in order to allow communications with one or more local or remote [[User (computing)|users]] using a [[Web browser|browser]]. The aim is to let users to interact with information provided by the embedded system ([[Web user interface|user interface]], data monitoring, [[Data logger|data logging]], data configuration, etc.) via [[Computer network|network]], without using traditional peripherals required for local user interfaces ([[Display device|display]], [[Computer keyboard|keyboard]], etc.).<ref>{{cite web |title=Administering Security for Oracle HTTP server |url=https://docs.oracle.com/en/middleware/fusion-middleware/web-tier/12.2.1.4/secure-ohs/administering-security-oracle-http-server.pdf}}</ref>

== 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]]print. The exact size depends on the system, but in many cases anything over several megabytes is not embeddable.

* Minimal [[CPU]] utilization.sdfdsf43

* Cross compilation support for multiple CPU and operating system combinations.

* Easy integration with an existing application, including static linking with the operating system and application.

* Serving pages from application memory 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 constraint and limit the choices of the system designer. [[C++]] or [[Java Virtual Machine|JVM]] availability for the system can be another constraint. Frequently performance is an issue, because typical embedded systems run multiple simultaneous tasks and an HTTP server is only one of them and may be configured as a low priority task.

In some cases the functionalities provided via HTTP server allow also program-to-program communications, e.g. to retrieve data logged about the monitored machine, etc.

== Known implementations ==

== Usages ==

*Inproc WebServer by [http://www.dcomlab.ru DComLab]. Single dll COM object, exposes ole-automation and IDispatch interfaces. Gives ability even to scripting languages to handle web requests with almost no effort.

Examples of usage within an embedded application might be (e.g.):{{citation needed|date=December 2021}}

*Windows' API Internet* family [http://social.msdn.microsoft.com/Search/en-US?query=InternetOpen&ac=8]

* Toto provide a [[thin- client]] interface for a traditional application..;

*C# Webserver [http://webserver.codeplex.com]. Webserver coded in C#, works with all .Net 2.0 applications.

* Toto provide [[indexingDatabase index|index]]ing, [[reportingreport]]ing, and [[debugging]] tools during the development stage.;

* Toto implement a protocol for the distribution and acquisition of information to be displayed in the regular interface — possibly a [[web service]], and possibly using [[XML]] as the [[Serialization|data format.]];

* Toto develop a [[web application]].

== Advantages ==

There are a few advantages to using HTTP to perform the above:{{citation needed|date=December 2021}}

* HTTP is a well studied cross-platform protocol and there are mature implementations freely available.;

* HTTP is seldom blocked by [[Firewall (computing)|firewall]]s and [[intranet]] [[Router (computing)|router]]s;

* HTTP clients (e.g. [[web browser]]s) are readily available with all modern computers.;

* Therethere is a growing tendency of using embedded HTTP servers in applications that parallels the rising trends of [[Home network|home-networking]] and [[ubiquitous computing]].

== Typical requirements ==

Natural limitations of the platforms where an embedded HTTP server runs contribute to the list of the non-functional requirements of the embedded, or more precise, embeddable HTTP server. Some of these requirements inare randomthe following ones.{{citation needed|date=December order:2021}}

* "Small" [[Random-access memory|RAM]] and [[Read-only memory|ROM]]print footprint. The exact size depends on the system, but in many cases anything over several megabytes is not embeddable.

* Minimal [[CPU]] utilization.sdfdsf43

* [[Cross compilation]] support for multiple [[CPU]] and [[operating system]] combinations.

* Easy integration with an existing application, including [[static linking]] with the operating system and application.

* Serving pages[[Web page|page]]s from [[Application software|application]] [[Computer memory|memory]] if there is no [[file system]].

* [[Modular programming|Modularity]].

* Single [[Thread (computing)|thread]] and [[Multithreading (software)|multi-thread]] support.

For every specific project, requirements can vary significantly. For example, ROM and RAM footprints can be a very serious constraint and limit the choices of the system designer. [[C++]] or [[Java Virtual Machine|JVM]] availability for the system can be another constraint. Frequently performance is an issue, because typical embedded systems run multiple simultaneous tasks and an HTTP server is only one of them and may be configured as a low [[Scheduling (computing)|priority]] [[Task (computing)|task]].

== See also ==

* [[Comparison of web serversserver software]]

* [[Comparison of lightweight webapplication servers]]

* [[Server (computing)]]

* [[HTTP server]]

* [[Web server]]

==References==

[[Category:Web server software| ]]

{{Reflist}}

== External links ==

{{software-type-stub}}

* [https://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] contains an extensive list of embedded HTTP server libraries towards the bottom of the page

{{network-software-stub}}

* [https://www.keil.com/pack/doc/mw/Network/html/group__net_h_t_t_p___func.html Example: functionalities of an embedded HTTP server component]

[[frCategory:Serveur Web Embarquéserver software| ]]

[[Category:Embedded systems]]