Feature #4267
Updated by Nicholas Gordon over 6 years ago
Currently, Currently NLSR maintains a separate set of separate classes and for encoding data structures for to TLV format. In my view, this is not an optimal approach. This is a simple problem to solve, since the purposes of data serialization. process is similar each time, and is a basic transformation to a string. This can be accomplished by a free function, for example, or by a method that employs a common helper function. Further, continually duplicating TLV classes is overly complicated and not viable in a tenable long-term design paradigm -- as the long-term. * NLSR number of published things increases, complexity of these structures will not duplicate existing data structures for increase, leading to double the purposes of serialization. maintenance work. We should aim to minimize the code surface, and only add complexity when necessary.