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

Post a Comment

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...
8 comments
Read more

Access Control

Access control is about controlling user flow within your application. Do not mistaken access control with security which is a bigger subject in itself. Access control begins by authenticating user and limit his or her activity in your application. An activity is something like creating, updating or deleting a content. There are always finite number of activities that can be done in a given application. Each user can be assigned to a set of activities that he or she is allowed to do. Access control is usually tied to session management. However, you do not need session management to have access control. When a user log in, a session is created so that the user is remembered for the subsequent access. Otherwise the user has to keep on providing his or her credential for each access. We can also keep a list of activities that the user is allowed to do in the session record. Some applications let the session alive indefinitely and some applications time out user after a duration of inacti...
Post a Comment
Read more

Separation of Front-end and Back-end Concerns

Separation of concerns is the cornerstone of MVC framework. Model, view and controller are three broad concerns of web-based software development. On its early days MVC was implemented on server side. The server renders views for clients. Nowadays, most clients render views themselves. Even the terminology of client-server has already morphed into front-end and back-end . The need for back-end to handle views is diminishing. View concerns have became increasingly complex with two big sub-concerns of aesthetic and dynamics. Front-end evolves into bigger MVC concerns of itself. While back-end evolves into larger modeling concerns. Now, front-end and back-end are two separate concerns. Front-end and back-end are handled by two different teams of software developers with different specialties. Back-end evolves into something like "dinner can be served even without plates, forks and spoons, without table and chairs, and without a dinning room." Front-end is serving the withouts....
Post a Comment
Read more