adrian-thurston / netp Goto Github PK

We want the broker to be able to write packets to the database, but it currently has no knowledge of what types of packets it can receive. It does not include the genf files of all the applications it receives packets from. In the current design, this information is dynamic. If we define a language for describing the structure of packets each application can transmit this structure to the broker before it sends a message of a particular type, and the broker can decode and insert into the appropriate database.

The grammar allows these, but it is causing a segfault in genf somewhere down the line.

Current problems with:

• absence of libares
• dh keys
• curl config check
• kring check
• postgres check
• ssl check