Varnish VCL, accomplishes the job, but far from elegant, of course.
It would be nice, indeed, to be able to start
from some template of a rules language.
Where
one can customize the 'language syntax' of declaring entities, and what to do with them.
And,then, to implement a domain-specific backend (either as code generated, or as interpreted at run-time).
I could not find a framework like that when looking for it, however.
( At the time, I was looking for something allows me to quickly build frontend, and backend runtime in language that can be embedded into java, C++ and javascript).
I started with metalua (this was years ago), and some success but was too difficult at the time to take it further.
Then I tried xText and xtend (so that I could get automatically an IDE.. but again was too difficult).
>
> "... The project I am currently working on involves receiving and processing gRPC messages from some A-brand network devices. The messages contain ordered sets of key-value pairs. The meaning and naming conventions for the keys and values varies greatly and is inconsistent across different message types. The problem was how to describe various processing rules for the messages...."
https://varnish-cache.org/docs/trunk/users-guide/vcl.html
Varnish VCL, accomplishes the job, but far from elegant, of course.
It would be nice, indeed, to be able to start from some template of a rules language.
Where one can customize the 'language syntax' of declaring entities, and what to do with them. And,then, to implement a domain-specific backend (either as code generated, or as interpreted at run-time).
I could not find a framework like that when looking for it, however.
( At the time, I was looking for something allows me to quickly build frontend, and backend runtime in language that can be embedded into java, C++ and javascript).
I started with metalua (this was years ago), and some success but was too difficult at the time to take it further.
Then I tried xText and xtend (so that I could get automatically an IDE.. but again was too difficult).
> > "... The project I am currently working on involves receiving and processing gRPC messages from some A-brand network devices. The messages contain ordered sets of key-value pairs. The meaning and naming conventions for the keys and values varies greatly and is inconsistent across different message types. The problem was how to describe various processing rules for the messages...."