Discussion
What if...?
http-server main {
bind "127.0.0.1:42069"
with script language=roto path="nsoe/main.roto" {
module "nsoe/module"
configuration-file "nsoe.kdl"
}
with metrics main
}
prometheus-server main {
bind "127.0.0.1:42042"
persist path=nsoe.json interval="1h"
}
And then, nsoe.kdl would contain the script's configuration. One could also opt to embed the configuration within iocaine's config file, using configuration { ... }.
I'm also entertaining the idea of merging all the *-server stuff into a single server:
server main protocol=http {
// former http-server configuration here
}
server metrics protocol=prometheus {
// former prometheus-server config here
}
server spoa protocol=haproxy-spoa {
// you know the drill
}
Simplifies the vocabulary, and the internal structures too.
In this case, I suppose I should rename with metrics $name to something like use metrics-server $name.
And now I wonder... do I need the use and with words? They might make it read more human, but... most of the configuration isn't that english-like.
So what if...?
server main protocol=http {
script language=roto { ... }
metrics-server prometheus
}
That feels ok. Without declare-handler, the script parts may have to be repeated if used in multiple servers, but:
server main protocol=http {
script path="nsoe/main.roto" {
module "nsoe/module"
configuration-file "nsoe.kdl"
}
}
server spoa protocol=haproxy-spoa {
script path="nose/spoa.roto" {
module "nsoe/module"
configuration-file "nsoe.kdl"
}
}
server garbage protocol=http {
bind "@haproxy-garbage"
script path="nsoe/garbage.roto" {
module "nsoe/module"
configuration-file "nsoe.kdl"
}
}
That's not too bed. A little repetitive with the module & configuration-file parts, but those don't need to be the same. They could be different, tailored to the particular server, like the scripts are.
A fun consequence here, with the three separate scripts that share the same configuration is that for SPOA, we do not need garbage generation, so that script would simply not load or prepare any garbage generation stuff.
That saves a whole lot of memory compared to 3.5.1, where, if you used NSoE, it would have loaded the training data even if it never used it.
Similarly, the nsoe/garbage.roto script would not set up matchers that are only needed for decision making. It would only do garbage generation.
Install bonfire.cafe
Get the full app experience
A couple of implications:
declare-handler: it's replaced withwith script, and is tied tohttp-server/haproxy-spoa-server.Currently, the module and the script must use the same language. But that limitation may end up lifted at some point, in which case
modulewill grow alanguage=$fooattribute.