Making a minimal web-application server #1

I expect a minimal web-application server to do two things:

serve semi dynamic html pages
provide an API interface to web-based client

Very simple HTTP-based API

You can create your API-s in plethora of ways, but I mostly used a very simple strpc "standard" to do my API-s for the last 14 years. It's very easy to create and serve an API on the server side and it's very easy to call such API. Any programming language, or a bash shell can do it without any special libraries. I called it strpc (SoTinyRPC) back then.

In short, a HTTP POST request to url like this:
www.example.com/API?_r=util&_m=add
with url-encoded arguments in a POST payload:
a=100&b=11

... would be an example of strpc call.

_r - defines resource
_m - defines method
_f - (optional) would define response format (json, csv, html, ...)
_x - (optional) would define explore mode (api self-documents itself)

You can make a strpc call from your shell using Curl command, for example:
curl -k \
-u $TOKEN:x \
-d "id=12&full_name=Jim&personal_tax_id=12345678" \
"https://www.example.com/API?_r=operator&_m=update"

First implementation

I wanted to define resources and methods of an API as naturally as possible. I used an ordinary context to define a resource. And created a webfn function, that defines our API methods. It uses Rye-s validation dialect do determine the validation rules of the method's arguments. Result of a webfn is encoded in JSON and returned to the client. If validation error happens, it is also returned as JSON to the client.

I needed two more functions to route to the right resource and select and call the right method.

Our application framework consists of just 5 functions so far, and does selection of resources and methods, JSON encoding, input validation and basic error handling .

Below is the code of a web-server, our "web-framework" and an example resource all on one screenshot. :)

You can get this example source code on github.

We will test and refine this in our next blogpost.

Komentarji

Priljubljene objave iz tega spletnega dnevnika

Less variables, more flows example vs Python

In the last blogpost ( Less variables, more flows ) I wrote a quick practical script I needed. It was an uncommon combination of CGI, two GET requests with Cookies and a POST request with Authorization header. I really like practical random/dirty problems, rather than ideal - made up problems to test the language. To get a sense of comparison I rewrote the example 2 times while removing specific Rye features. But that comparison is meaningless to a person that doesn't know Rye or at least Rebol already. So I went on fiverr and made a request for a Python script with these requirements. I got a nicely written Python script that uses functions for each step. To be more comparable, I rewrote the Rye code to a similar structure. Below is the result ... For a next step, it would be interesting, to extract a little simpler example out and add error handling. With Rye-s specific failure handling, I think the difference would become even greater. You can find Rye on github .

Preberite več

Ryelang - controlled file serving example and comparison to Python

This is as anecdotal as it gets, but basic HTTP serving functions in Rye seem to be working quite OK. They do directly use the extremely solid Go 's HTTP functions, so that should be somewhat expected. I made a ryelang.org web-server with few lines of Rye code 3 months ago and the process was running ever since and served more than 30.000 pages. If not else, it seems there are no inherent memory leaks in Rye interpreter. Those would probably show up in a 3 month long running process? And now I got another simple project. I needed to make a HTTP API for some mobile app. API should accept a key, and return / download a binary file in response if the key is correct. Otherwise it should return a HTTP error. So I strapped in and created Rye code below. I think I only needed to add generic methods stat and size? , all other were already implemented, which is a good sign. Of course, we are in an age of ChatGPT, so I used it to generate the equivalent Python code. It used the elegant

Preberite več

Receiving emails with Go's smtpd and Rye

This goes a while back. At some project for user support, we needed to receive emails and save them to appropriate databases. The best option back in the day seemed project Lamson . And it worked well ever since. It was written in Python by then quite known programmer Zed Shaw. It worked like a Python based SMTP server, that called your handlers when emails arrived. It was sort of Ruby on Rails for email. We were using this ever since. Now our system needs to be improved, there are still some emails or attachments that don't get parsed correctly. That isn't the problem of Lamson, but of our code that parses the emails. But Lamson development has been passive for more than 10 years. And I am already moving smaller utilities to Rye. Rye uses Go, and Go has this nice library smtpd , which seems like made for this task. I integrated it and parsemail into Rye and tested it in the Rye console first. Interesting function here is enter-console , that can put you into Rye console any

Preberite več

ryelang

Preišči ta spletni dnevnik