stop=false query parameter is never used

[Israel77]

The protocol specifies a boolean query parameter stop, which is set to true if the client just want to send the analysis result without acquiring the next job, or false if the client would like to acquire the next job immediately.

However, I noticed that the client always sends the query parameter as stop=true, there is no flag or configuration option to change this behavior. Even if I change the code responsible for the request to send stop=false instead, the rest of the client code does not expect the 202 Accepted response from the server when sending an analysis.

Are there plans to use allow the client to set this query parameter to false? Seems like it would be a nice option for dedicated machines. Also, if I implement an alternative fishnet client, would it be safe to pass this query parameter as false?