PRRT merge requestshttps://git.nt.uni-saarland.de/LARN/PRRT/-/merge_requests2020-11-26T11:55:56Zhttps://git.nt.uni-saarland.de/LARN/PRRT/-/merge_requests/7Use full url for XLap dependency2020-11-26T11:55:56ZSven LiefgenUse full url for XLap dependencyUsing the relative path made it impossible to fork the project without also forking XLap as well as using it somewhere that relied on an actual url being given, like cargo.Using the relative path made it impossible to fork the project without also forking XLap as well as using it somewhere that relied on an actual url being given, like cargo.https://git.nt.uni-saarland.de/LARN/PRRT/-/merge_requests/6Oxidize delivery store2020-09-04T08:24:22ZSven LiefgenOxidize delivery storehttps://git.nt.uni-saarland.de/LARN/PRRT/-/merge_requests/5Oxidize packet delivery store2020-08-28T11:32:14ZSven LiefgenOxidize packet delivery storehttps://git.nt.uni-saarland.de/LARN/PRRT/-/merge_requests/4Implementation dependant behaviour2020-11-03T10:33:31ZSven LiefgenImplementation dependant behaviourIn the current code, en/decoding of a block uses casts and memcpy to get from Payload to Buffer and vice versa.
I.e. the whole payload is copied into a buffer including the header information. This buffer is then encoded via FEC and send...In the current code, en/decoding of a block uses casts and memcpy to get from Payload to Buffer and vice versa.
I.e. the whole payload is copied into a buffer including the header information. This buffer is then encoded via FEC and send.
I think this makes the protocol implementation dependent, as not all implementations will use the same internal representation.
This merge request should fix this by encoding the Payload into the wire format as described by the protocol before encoding using FEC.Pablo Gil PereiraPablo Gil Pereira