Description
The following ideas were raised by @rjb1000. I am putting them here for further discussion to not lose track of it. The idea is to make the FLUTE library more flexible with respect to handling of unknown TSI:
- Should there be a mode of operation where one TSI is nominated as a command line parameter, and only packets belonging to that are processed by the client?
- Should there be a "strict" mode of operation where the client exits with an error if it encounters packets with a different TSI value that expected rather than simply ignoring them?
- When operating in "promiscuous" mode (i.e. packets with any TSI are processed), should the recovered files be sorted into different reception subdirectories in the local file system?
Description
The following ideas were raised by @rjb1000. I am putting them here for further discussion to not lose track of it. The idea is to make the FLUTE library more flexible with respect to handling of unknown TSI: