When to fetch <variant, chain, realization> triplet

[JannisBush]

Currently, we fetch this information in the init view at the beginning of the experiment.
If somebody takes a long time reading the instructions or does not even presses the next button, another participant might has to wait a long time, because they are already matched by their triplets.

Only fetch this information, when a participant is ready for the experiment and presses the to the lobby button.

[JannisBush]

An easy solution is to just change the position of the init view and to put it between the instructions and the lobby.
This could be a problem, if the user can't connect to the server and starts the experiment by reading the experiment (on crowd working platforms).

A more elegant solution could be to first only connect to the participantChannel to see if there are any slots left in general, but only fetch the information and assign the user a triplet, if the client sends a ready - message to the participantChannel after the user clicks on the to the lobby-button.

[x-ji]

I think this might also be helped by the timeout implementation we discussed before. i.e. if the participant didn't move for 10 minutes, the connection will be dropped and they will be prompted to try again. Might also be a solution.