Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Subject: Re: Lua co-routines
To: dev@apr.apache.org
References: <6CE4A24A-6A55-4B98-B058-F3D33B17C7BD@jaguNET.com>
From: =?UTF-8?Q?Branko_=c4=8cibej?= <brane@apache.org>
Organization: The Apache Software Foundation
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAAXNSR0IArs4c6QAAADBQTFRF
 IhsbCy0qZjoVOVRoeFxSAIKBzXQiAKaibYiewnk7nn9z0qCTgL3i87Ep6Kx/+tHBsrE+zgAAAjZJ
 REFUOMvF0jFoE1EYB/CzjWlqIzaTjqVIBifRRWyG0t5iUqlLyFpCeXBgKg5yq6A4degUDJjoUDpc
 1Qt4Ux94B11SOLB0KGS4discpbkORTCn9/m9d3fvLhXnvuHu3f+Xx/veyyfZfLSdZHzgicSfeyw4
 JISwdz8FT6M8lM8Ceg385Dlhs+cC9sQCDn0B78QCogzwN+sxfHGOIXBbRGkNAM4cZymGtgNsDPgz
 cByxon3EEm1TLmvAlghoHOO3CZSa+IQ/vF6JV8tgKOMow78gRgL2/+EIvATOUtB3SSdMg4GXgrbn
 uk0uLiGdoCHKbX4E+t1FUTqn1AtIdPJebssDQ64YANSQyyaQNyUOFs0ijMsMFnOPTahPLXKYowtY
 08MfCP7vR7hRnc5zmPK7CDYYbHcbC7tHuyFA94U/1LYZaJpu/sxACHMwvwZljTLY0TbNk4x+zuEt
 yC3MfCM6uSIvfwur0itFL4FA2Yal8BzLfnYV4EIGwEPAk7o5zIcnvzHMEjwJrrhAKK7on6IrsfRJ
 7A53BhaK+CL7fj6+q/sPeOvcDTtoZTxpUYsFeIknrOXep3p3l7Ua+8sZ5FPQKyKwWi+DfROTU7ny
 C1/9UhpeY7K287WJCzbsNPQm2S6Yk4PSCNhWM2r3nD0K9liYb6yPgCRJhSzPrxUK0yUBVk1VX0lj
 s7MzGZyp0wImMK/e8rHbz2soL+O+2r1dxfGsAmBcx0lNjS/RUhlUC7gRn1wGMdQ7Vw1/AReW/RN3
 xFWdAAAAAElFTkSuQmCC
Message-ID: <5606EDD3.90802@apache.org>
Date: Sat, 26 Sep 2015 21:11:15 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <6CE4A24A-6A55-4B98-B058-F3D33B17C7BD@jaguNET.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 26.09.2015 19:10, Jim Jagielski wrote:
> I've been keen on libmill, which provides a golang-like
> goroutine library. It seems that such functionality would
> be cool for APR and APR-based apps (like serf and httpd).
>
> Then I started thinking: Lua also has a great coroutine impl
> and it is also MIT licensed and might be easier to fold
> into APR. Anyone ever look at that? Having something like
> apr_routine() would be awful cool.

Whilst I agree that co-routines are useful, I don't see a good reason to
fold this into APR. I feel that APR has already departed far from its
"portable runtime" promise. With database connectors and whatnot it's
become a bit of a mastodont. We really should rethink what we're doing
here; APR is no longer the "Apache (httpd) Portable Runtime", it's used
by other projects that don't need all the luggage.

And furthermore, it's not 1999 any more: the reasons why it was a good
idea to bundle, e.g., an XML parser or a BerkeleyDB frontend into APR
are no longer valid. I wish we'd pared APR-2.0 down to the basics of
memory management, filsystem and I/O abstraction. We surely don't want
to invent yet another coprocessing library.

-- Brane