Your flag #:blocking? #true would do a per-connection thread, which while
implementing lack of blocking, is a stronger property than non-blocking. Also,
(kernel-level) threads have some overhead, which is sub-optimal;
Instead of a flag, I propose defining a new ‘server-impl’
Web Server (Guile R
concurrently because of
the coroutine based on delimited-continuation.
Of course you may enhance it with thread pool.
Best regards.
On Mon, Mar 25, 2024 at 4:04 AM Ryan Raymond wrote:
> Hello, all.
> I was able to build a non-blocking web-server using network sockets.
> However, the
On Sun, Mar 24, 2024 at 03:41:32PM -0400, Ryan Raymond wrote:
> Hello, all.
> I was able to build a non-blocking web-server using network sockets.
> However, the existing guile web/server.scm implementation is
> single-threaded and therefore blocking [...]
How does "singl
Hello, all.
I was able to build a non-blocking web-server using network sockets.
However, the existing guile web/server.scm implementation is
single-threaded and therefore blocking, which is sub-optimal for some
use-cases.
I suggest we slightly modify the server logic to have an optional
