Preface

With the invent of async based programming for I/O bound tasks, it will be faster to fetch remote resources without waiting for the result before issuing another fetch requests.

This concurent mechanism allows more than one resource to be fetched at a time in a single request session.

The Evolution of Script Based Web App

Ok, the are several tech stack that powers dynamic web sites.

• cgi: Common Gateway Interface. Used to execute a single oneshot script. Each request to cgi resource is served by a new cgi process. The home page of this tilde is calling /cgi-bin/neofetch.cgi to display current system information.
• fastcgi: Like cgi, but using process pre-forking to execute cgi faster, removing the overhead of process creation. Notably used with php.
• wsgi: Web Server Gateway Interface. Like fastcgi but very much of it is for python web app. Still synchronous, i.e. serving a single request at a time. Notable application server using this tech is uwsgi, gunicorn, and waitress. Asynchronous capability can be achieved using threads or green threads like greenlet or gevent.
• asgi: Async Web Server Gateway Interface. Like wsgi, but with additional capability to serve multiple requests at a time. Notable users are hypercorn and uvicorn.
• rsgi: An interface lower level than asgi, i.e. interacting at protocol level and with multi-programming language interaction. Notable user is granian web server framework.

Previously, I have experimented with a wsgi web app. Now I want to experiment with asgi web app.

The ASGI Web App

Well, it is just a simple watch page for some vod platforms. Just click the link below to access the web app.

Quarttube Web App

Since this is just an experiment, there is no guarantee that the web app will be available all the time. So there is no uptime guarantee for this web app.

Thanks for your interest in my tilde project.

Feel free to support the author on Ko-Fi. Your generous support is greatly appreciated.

Back to main page