Skip to main content

libesphttpd and Micro API

libesphttpd is a HTTP server library for ESP8266. It has a fair documentation on Github and a demo. It supports common gateway interface (CGI) in C. It also has a tool to compile a collection of web pages into a binary blob which is to be flashed into ESP8266 separately from the web server codes. It can host static web files. In general, libesphttpd can be used to build a complete web server for ESP8266.

However, ESP8266 is too tiny for a full blown web server.

It is a standard practice to separate the development of web pages and a web server. In fact, due to the limited resources of the ESP8266, the web server should be kept to minimum by only exposing APIs. The web pages should be designed as the applications that run at the client side.

I wrote a micro-api framework using libesphttpd and esp-open-sdk.

Separation of concerns is important in web application development since it involves multiple stacks of tools. On the server side there will be embedded C-based tools. And on the client side there will be HTML, Javascript and CSS. The C codes for the server will have to be routinely compiled and flashed into the ESP8266 throughout the development. On the other hand, the web application development can be contained temporarily in localhost. HTML, Javascript and CSS are all scripts that do not need to be compiled. And they don't need to be flashed all the time throughout the development.

The web server is tiny. The memory is tiny. The database is as good as a flat file. Don't expect it to be an ordinary web server. The server's C codes have to be thoroughly optimized. Otherwise, the ESP8266 will be left with too little resources for it to do its embedded things.

Hence, micro API is the solution.

We can use various web frameworks on the client side. However, the total size of the files used must not reach the limit of the available flash memory in the ESP8266. Hence, we do have a development constraint on the client side. Fortunately, there are many thin front-end web frameworks for us to choose from and assemble.

Anyway, we are building the Internet of Things (IoTs). If we need a bigger web server then we should not be doing it on ESP8266.


Comments

Popular posts from this blog

Setting Up PyScripter for Quantum GIS

PyScripter is a general purpose Python Integrated Development Environment (IDE). Quantum GIS (QGIS) is a desktop GIS application that can be extended with Python plugins. Both are open source softwares. We intend to use PyScripter as an IDE to build QGIS Python plugin. We are using PyScripter 2.4.1.0 and QGIS 1.6.0 in Windows. PyScripter does not come with Python. On the other hand, QGIS is built in with Python. Thus, we will setup up PyScripter to use the build in Python in QGIS. We assume both PyScripter and QGIS are already installed. Preparing PyScripter batch file We assume that QGIS is installed in C:\OSGeo4W\ folder and PyScripter is installed in C:\Program Files\PyScripter\ . 1. Copy qgis.bat in C:\OSGeo4W\ bin to pyscripter.bat 2. Edit pyscripter.bat to remove the last line that read something like this start "Quantum GIS" /B "%OSGEO4W_ROOT%"\apps\qgis\bin\qgis.exe %* and replace it with this in one line Start "PyScripter" /B "C:\Progr...

Using React in Foundation for Sites

This post was the precursor to the Foundation-React Template . React and Foundation are two different web UI frameworks addressing different needs. They evolve differently. Both of them are powerful on their own accord. Fusing them together may create superpower. We will walk through the process of adding React into Foundation. We will start by installing both Foundation and React through command line interface (CLI). Then we will create a simple Todo web app. Along the way we will highlight the development process. But before all that, let us summarize React and Foundation. The details can be found at their respective websites. Both of them are well documented. React is a run-time UI rendering engine. It renders dynamic UI elements in its own fast virtual DOM, and only update necessary changes to the slow browser DOM. This behaves like a  double buffering DOM which makes any UI update feels fast. React wraps a UI rendering script in a component. A React component can ...

Debugging PHP using Apache Error Log

PHP runs on the server side and behaves like a function that return a value against the given arguments. A remote client may call this function and expect a specified return value and nothing else. So how do we debug this function ? It must not return debugging messages since the client is never designed to handle them. We must never burden any client to handle debugging messages. If we run PHP through Apache server then we can use the error log to keep our debugging messages. It may not be the best way to do it. But we only want to talk about this approach now. Error Logs The Apache error log files generally can be found in the following directory: var/log/apache2 We issue the following command from within the directory to read the latest error messages: # tail error.log The tail command reads the last few lines from the error.log file and prints them on the terminal. If we need to read a specific number of lines from the end of the file then we can specify the -n opti...