I agree with you, but why does not the community migrate to a modern feature
rich solution? From your words, I think this has been an already discussion
here.
Hi,
Is there a way tu subscribe to forum threads, users and/or categories?
Well, it has been 2 years since the last post, and I wonder what is the state
of Nim regarding IO and CPU intensive work.
I personally like Rust's multithreaded async (the chance to be able to opt-in,
in fact) for IO tasks; and also Go goroutines, useful for both IO and CPU
tasks. Does Nim has
Web servers do not fork a new process for each request. Processes are too heavy
to use one per request. They usually spawn only one process per CPU core, and
each process deals with a lot of requests.
Thank you. That is exactly what I was looking for. One question, do I need one
different newAsyncHttpClient for earch request?
I do not understand why FastCGI should be faster when app cache does not work.
Well, if you already have a good http server, why do you ever need a FASTCGI
protocol implementation?
In addition, the fact that you need a frontend for https or compression does
not mean you cannot implement them, as a part of the HTTP protocol, and get rid
of NGINX or Apache. As far as I know
I am trying to fetch some urls asynchronously, and I am getting a weird
behavior I do not expected.
proc fetchAllAsync*(urls: seq[string]): Future[seq[string]] {.async.} =
var c = newAsyncHttpClient()
for url in urls:
debugEcho &"Before {url}"
result.add(a
