The testbed currently implements a pretty flat interaction between peers and network. We choose the files to seed to the network, seeders Add these files to the network, and leechers flatly Getthem. No complex interaction pattern is implemented. Instead of exclusively choosing the files to be used in the test, we should implement an interactionFunction which is fed to the testbed to simulate different applications and request patterns in the test runs.
defaultInteraction: Flatly Add/Get Files.
getAllLeavesInteraction: Retrieves the files of a DAG.
databaseInteraction: Performs read/write operations over DAGs implementing a database schema.
etc.
This needs to be implemented as general as possible so that anyone could come up with their own interactionFunction and plug it into the testbed.
The testbed currently implements a pretty flat interaction between peers and network. We choose the files to seed to the network, seeders
Addthese files to the network, and leechers flatlyGetthem. No complex interaction pattern is implemented. Instead of exclusively choosing the files to be used in the test, we should implement aninteractionFunctionwhich is fed to the testbed to simulate different applications and request patterns in the test runs.defaultInteraction: Flatly Add/Get Files.getAllLeavesInteraction: Retrieves the files of a DAG.databaseInteraction: Performs read/write operations over DAGs implementing a database schema.interactionFunctionand plug it into the testbed.