3604046f68
Make the Interpreter be able to handle SimulatorTransport as well. This includes introducing changes that make it possible to use the different transport types in a semi-polymorphic way with the introduction of factory methods in the RequestRouter. The reason for this solution is that the classes that represent the different transport types have member function templates, that we can not make virtual. This solution seemed to be the least convoluted. In the testing itself now it is possible to pass a set of cypher queried to the interpreter which would run these queries against the interpreter and the individual shards that are managed and started up by the MachineManager with the different entities communicating over the simulated network. |
||
---|---|---|
.. | ||
benchmark | ||
concurrent | ||
drivers | ||
e2e | ||
gql_behave | ||
integration | ||
jepsen | ||
macro_benchmark | ||
manual | ||
mgbench | ||
property_based | ||
public_benchmark | ||
simulation | ||
stress | ||
unit | ||
.clang-tidy | ||
client-stress.sh | ||
CMakeLists.txt | ||
setup.sh |