Allow forcing SliderServer POST request using notebook metadata #2362
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add the possibility of forcing Pluto to always use POST requests when requesting updates from a SliderServer.
Done by using a custom field in the notebook metadata.
This is mostly useful to avoid caching of the reply in cases where one has results that depend on random values and prefers to always get new random results for the same bond variables.
It is also useful to have SliderServer work better when one uses
@bindcalls generated inside custom made macros that are not correctly parsed by PlutoSliderServer to generate the bond graphThe easiest way to disable caching by enabling this feature is opening your notebook file (on the server) and adding this line at the beginning of the notebook
So that your notebook file starts like this (for example):