My situation is the following.
I use a Perl Dancer API application (with Starman). My main client timeout after 10 seconds. But the Dancer process still run after if the request is really big (BigData project) then if a client call the API on the same server instance which still run then it doesn't answer.
Is there a way to set a timeout to Dancer which stop the execution of the current process ?
At the Dancer app level, there is currently no such thing, as the app just send things along to the plack layer, without any question nor follow-up. What I can check is if we can have Dancer deal with streamed answers, and verify if those would stop sending if the client closes the connection.
We have the streaming wish at #1002, so I'll close this ticket.