On 3/31/09 10:18 AM, "Bertrand Mansion" wrote:
> Reading the comments in your code, it seems that mod_lua could benefit
> from a better error reporting ?
Perhaps. Or I just needed to actually add error checking Right now I
rely on the lua side to sanity check stuff.
--
Brian Akins
Chief O
prueba
-Original Message-
From: Graham Leggett [mailto:minf...@sharp.fm]
Sent: Lunes, 30 de Marzo de 2009 08:03 p.m.
To: dev@httpd.apache.org
Subject: Re: what is in modules vs what is in the core
Paul Querna wrote:
> mod_watchdog is the latest offender in a series of modules t
Le 31 mars 09 à 15:52, Akins, Brian a écrit :
OT, but will you contribute that to mod_lua ? :)
Based on mod_memcache and mod_wombat . For demonstration only as
this uses
our hacked version, but you get the idea how simple this was. Build
it in
lua dir like /usr/lib/lua/5.1/apach2/memc
> OT, but will you contribute that to mod_lua ? :)
Based on mod_memcache and mod_wombat . For demonstration only as this uses
our hacked version, but you get the idea how simple this was. Build it in
lua dir like /usr/lib/lua/5.1/apach2/memcache.so
--
Brian Akins
Chief Operations Engineer
Tur
Paul Querna wrote:
mod_watchdog is the latest offender in a series of modules that expose
additional functions to the API. (mod_proxy and mod_cache do too!)
So, you came back from different direction, cool :)
If you really like to put the watchdog functionality
inside the mpm (and IMO that's
> -Ursprüngliche Nachricht-
> Von: Paul Querna
> Gesendet: Dienstag, 31. März 2009 01:37
> An: dev@httpd.apache.org
> Betreff: what is in modules vs what is in the core
>
> mod_watchdog is the latest offender in a series of modules that expose
> additio
On Tue, Mar 31, 2009 at 4:25 AM, M. Brian Akins wrote:
> As I hack on some lua stuff, it's useful to have the symbols for functions.
> That may just be because I'm lazy, because I could do optional function
> lookups in library opens, I suppose. OT, but I like my Lua glue in a lua
> module and
Maybe a more layered approach would be something to consider for 3.0?
Seems to me that the layers and groups of modules keeps expanding and expanding.
2.0 -> 2.2 had the whole auth move over so maybe it's time to rethink
the current module system for 3.0?
~Jorge
On Tue, Mar 31, 2009 at 4:25 A
On Mar 30, 2009, at 7:37 PM, Paul Querna wrote:
mod_watchdog is the latest offender in a series of modules that expose
additional functions to the API. (mod_proxy and mod_cache do too!)
What happened to all functions that are not inside server/* must be
either dynamic optional functions or hoo
Paul Querna wrote:
mod_watchdog is the latest offender in a series of modules that expose
additional functions to the API. (mod_proxy and mod_cache do too!)
What happened to all functions that are not inside server/* must be
either dynamic optional functions or hooks?
Doesn't anyone remember t
mod_watchdog is the latest offender in a series of modules that expose
additional functions to the API. (mod_proxy and mod_cache do too!)
What happened to all functions that are not inside server/* must be
either dynamic optional functions or hooks?
Doesn't anyone remember the load order pain of
11 matches
Mail list logo