Hi Juliusz,
On Thu, Mar 15, 2018 at 12:37:55AM +0100, Juliusz Chroboczek wrote:
> https://github.com/christf/libbabelhelper
When you feel you're ready, please provide me with a one-line
description,
and I'll add a link to the Babel page.
I just pushed a set of improvements to the library
> https://github.com/christf/libbabelhelper
When you feel you're ready, please provide me with a one-line description,
and I'll add a link to the Babel page.
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
Juliusz Chroboczek writes:
>> In this example, parsing the custom format in Python would be something like:
>
> No, parsing input using string.split is always incorrect. You really
> want to write a proper lexer.
>
> The lexer I posted above is 70 lines of C, including full error
>
> The main benefit of a well-known format is that the requirement for a
> client goes from easy parsing code to *no* parsing code.
Right. So either we add a dependency on JSON to babeld, or we add
a trivial parser to every program that consumes babeld's input.
> In this example, parsing the
> I agree that the current format is very easy to parse for a human, which
> is a benefit. I am struggling to have a machine parse this though.
You need a lexer. Here's a simple lexer for you:
https://www.irif.fr/~jch/software/babel/babel-lexer.c
-- Juliusz
Juliusz Chroboczek writes:
>> Nils and I wrote such a daemon, called mmfd. It is able to forward
>> multicast packets in the whole network. To learn about the topology and
>> the relevant neighbours, it queries babeld: mmfd is listening via
>> "monitor" on the babeld socket.
>
>
What do you think of providing the same data over json to make it better
parsable?
The format of the monitoring interface is well defined : it's a series of
lines of the form
keyword id key value key value ...
where each key/value is either space separated, or a string within double
quotes.
> Nils and I wrote such a daemon, called mmfd. It is able to forward
> multicast packets in the whole network. To learn about the topology and
> the relevant neighbours, it queries babeld: mmfd is listening via
> "monitor" on the babeld socket.
Good.
> What do you think of providing the same
Hello,
when building a large mesh network, Freifunk communities use maps such that
users can find nodes in the real world.
For this there must be a daemon collecting telemetry in the network.
This daemon must know a little bit about the network topology, at least
its neighbours.
Nils and I
9 matches
Mail list logo