> > You can also do it once in a utility class. It doesn't have to be a layer > > as such, you can just write some functions to decode strings into types > > and then put them in a library. > > Thats what we do currently, but as Oskar pointed out, it introduces a > spaghetti of dependencies throughout the code that are difficult to change > and tough to justify.
If you put all the methods for encoding/decoding various types in a utility class then you can have calls to the utility class throughout the code. That's just one dependency and you can change the utility class whenever you want to affect global changes in encoding. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
