Re: Release: serverino - please destroy it.

On Monday, 9 May 2022 at 20:08:38 UTC, Sebastiaan Koppe wrote: On Sunday, 8 May 2022 at 21:32:42 UTC, Andrea Fontana wrote: Every request is processed by a worker running in an isolated process, no fibers/threads, sorry (or thanks?) I did some tests and the performance sounds good: on a local

Re: Release: serverino - please destroy it.

On Sunday, 8 May 2022 at 21:32:42 UTC, Andrea Fontana wrote: Every request is processed by a worker running in an isolated process, no fibers/threads, sorry (or thanks?) I did some tests and the performance sounds good: on a local machine it can handle more than 100_000 reqs/sec for a simple

Re: Release: serverino - please destroy it.

On Monday, 9 May 2022 at 19:09:40 UTC, Guillaume Piolat wrote: On Sunday, 8 May 2022 at 21:32:42 UTC, Andrea Fontana wrote: Hello! I've just released serverino. It's a small & ready-to-go http/https server. Dub package: https://code.dlang.org/packages/serverino Andrea Looks very useful, c

Re: Release: serverino - please destroy it.

On Sunday, 8 May 2022 at 21:32:42 UTC, Andrea Fontana wrote: Hello! I've just released serverino. It's a small & ready-to-go http/https server. Dub package: https://code.dlang.org/packages/serverino Andrea Looks very useful, congratulations!

Re: Release: serverino - please destroy it.

On Mon, May 09, 2022 at 04:48:11PM +, Vladimir Panteleev via Digitalmars-d-announce wrote: > On Monday, 9 May 2022 at 16:37:15 UTC, H. S. Teoh wrote: > > Why is memory protection the only way to implement write barriers in > > D? > > Well, it's the only way I know of without making it a major

Re: Release: serverino - please destroy it.

On Monday, 9 May 2022 at 16:37:15 UTC, H. S. Teoh wrote: Why is memory protection the only way to implement write barriers in D? Well, it's the only way I know of without making it a major backwards-incompatible change. The main restriction in this area is that it must continue working with c

Re: Release: serverino - please destroy it.

On Mon, May 09, 2022 at 05:55:39AM +, Vladimir Panteleev via Digitalmars-d-announce wrote: > On Monday, 9 May 2022 at 00:25:43 UTC, H. S. Teoh wrote: > > In the past, the argument was that write barriers represented an > > unacceptable performance hit to D code. But I don't think this has > >

Re: Release: serverino - please destroy it.

On Mon, May 09, 2022 at 05:52:30AM +, Vladimir Panteleev via Digitalmars-d-announce wrote: > On Sunday, 8 May 2022 at 23:44:42 UTC, Ali Çehreli wrote: > > While we are on topic :) and as I finally understood what > > generational GC is[1], are there any fundamental issues with D to > > not use