ErlWeb is the package that contains the HTTP and FTP protocols and a few other goodies.
The HTTP protocol will be served by the Erlang Web Server (EWS) which is going to be an HTTP/1.1 compliant web server with as many standard extension as I can mange to create. I already have the scanning and parsing routines down for HTTP messages and I have the base code done for the communications side as well.
While all of that can be used now with the built in HTTP server and/or YAWS the part that is motivating me to create EWS is a built in markup language that I am developing called Erlang Markup Language (ERML). This language will be similar to other markup languages like HTML, but it will have the scripting capabilities of a server side language and be extendable by any erlang module on the system.
ERML will be compiled into BEAM files so that they are easily run by any Erlang system and a caching system will detect when a file has changed and it will re-compile the file into a new BEAM file and reload the newer version into the system. This will allow for easier updating of web sites and faster development times.
I believe that ERML will eventually create a group of programmers that know how to use ERML, but may not know how to write programs in Erlang. This will hopefully expand the overall Erlang user base and open up new markets, including writing Erlang modules that are specifically meant to be used in ERML web based applications.
I have written two prototypes of the scanning and parsing routing for ERML and I’m not quite happy with them yet. I have extensive notes on how the languages is going to be implemented and I just need to find the time to create it 
Erlang, ErlWEb, ERML, Erlang Markup Language
Technorati Tags: Erlang, ErlWEb, ERML, Erlang Markup Language
