Building Server-Side Web Language Processors


On recent entries, we have been discussing about compilers, their purpose, how they are built and how they have helped the programming environment evolve. Now, we will be discussing about the same compilers we have talking about but, instead of running in our local device(s) from a command-line shell, these compilers will be running on the web.
Nowadays, most of the software applications are implemented with web resources due to the high demand. However, not only applications can be done with web resources; also, compilers can be created like that.

Nevertheless, building a web-based compiler is not only coding a translator or parser, it can be similar to another programming language that already exists, but also you need to be careful and pay attention to other concepts like rules, syntax, security, protocols and naming.  

On the other hand, talking about the server side, you need to check which implementation strategy is going to be used, as well as the uses of the Common Gateway Interfaces (CGI), which is an interface that runs programs under a web server, and the development of your own server.

It is important to keep in mind that, even though you are going to develop a new language interpreter and/or a server, you do not have to create or invent everything. In order to make the process easier as possible you might consider the fact that now we have existing web technologies and documentation that might be helpful during the process and that these tools can save you some time.

As Computer Science engineers, we need to understand and apply our knowledge to develop good services. I mean, in this case, you have to know how the web environment works and how it is supported because it is an area that will be used or some many year, as well as the interpreters and programming languages.

Comentarios