Different levels of concurrency for post and get routes. #148
Description
I am setting up an app that needs different levels of concurrency, at least I think that is the solution. The main .route is a process intensive POST request that can take some time needs to be uninterrupted and ideally queued, the others provide update status and documentation which do not affect the running and are very useful. I found that sending a POST request before the previous was complete crashed the system. I don't want to close the port while the task is running, and I'm not sure that will work anyway and it will look like the server has become unresponsive either . Is there any in built solution I have missed, or workarounds I can try?