I separated the parser logic from the server logic (thank you Kai for his comment on #24 (https://github.com/openalto/ietf-hackathon/issues/24)). Now, the parser lives in a G2Parser class that is used in the server. Note that parser code can easily be swapped out, if we want to develop another parser, as long as the parser implements a method construct_from_flows(flows_list).
I separated the parser logic from the server logic (thank you Kai for his comment on #24 (https://github.com/openalto/ietf-hackathon/issues/24)). Now, the parser lives in a
G2Parser
class that is used in the server. Note that parser code can easily be swapped out, if we want to develop another parser, as long as the parser implements a methodconstruct_from_flows(flows_list)
.