Asynchronous processing of http requests vs spawn tasks!

Async suitable for IO intensive task, multi-thread model suitable for cpu intensive task.

Asynchronous processing of http requests vs spawn tasks!

This is another example of handling requests with spawn: I believe [GuildenStern](https://github.com/olliNiinivaara/GuildenStern) does something like this internally as well. I'm doing it in one of my projects because i just find it simpler and i never have

Asynchronous processing of http requests vs spawn tasks!

Is there any advantage to using spawn tasks instead of asynchronous processing of http requests? Is it faster to process the requests? My idea was to use the same approach that golang uses with goroutines. Many Nim libraries does not have asynchronous support. Code from asynchttpserver: