On Thu, Feb 5, 2009 at 9:39 PM, Brian McCallister wrote:
> I can see how this fits with the spec, but I'd still prefer to find a
> different way to pass that information. One way, though I do not like
> it much more, is to pass the bytecode in as the filename and look for
> lua bytecode's initial
On Thu, Feb 5, 2009 at 9:21 PM, Brian McCallister wrote:
> It looks like fields were added to apl_vm_spec to allow for bytecode
> caching on the actual spec. I think this is a bad idea. Specs are
> short-lived, typically stack-allocated, structs which exist to group a
> bunch of arguments togethe
It looks like fields were added to apl_vm_spec to allow for bytecode
caching on the actual spec. I think this is a bad idea. Specs are
short-lived, typically stack-allocated, structs which exist to group a
bunch of arguments together.
If we choose to re-enable bytecode caching in mod_lua, it shoul
Paul and I seem to be stepping on each others toes, so I want to
settle on how lua_State (vm) management should work.
My opinion:
* VMs are attached to apr pools.
* A pool may have several VMs attached to it
Each VM has a name, that name is part of the key in the pool
userdata key.
* Concur
Pierre,
I spent 10 hours trying to compile. I tried different orders.
I tried so many variations it was maddening.
Anyway, I wound up not needing the crypt function after all.
I thought I was suppose to be using encrypted passwords. What I was really
supposed to be using was encrypted digest.
Maybe, I'm not on the right forum. I posted and go no response.
I guess that's ok. I got mod_auth_digest authenticating against mysql
working. I need to make it prettier. I didn't want to disturb the existing
code, so I was super cautious. My only issue now if changing the password.
There was
On 2/5/09 1:51 PM, "Brian McCallister" wrote:
> Yep, Paul changed the internal impl to be less gross, but in doing so
> changed the API, i changed the impl to be not gross and restored old
> API.
Okay I see it now.
I may take a crack at a little performance tuning. Setting up the dispatch
tabl
On Thu, Feb 5, 2009 at 10:44 AM, Brian Akins wrote:
> Is this in trunk? I don't see it, but I've been known to overlook stuff.
It is in trunk (httpd trunk)
>
> On 1/26/09 1:45 PM, "Brian McCallister" wrote:
>
>> For anyone following, it has been applied :-)
>>
>
>>>
>>> -- NEW
>>> f
Is this in trunk? I don't see it, but I've been known to overlook stuff.
On 1/26/09 1:45 PM, "Brian McCallister" wrote:
> For anyone following, it has been applied :-)
>
>>
>> -- NEW
>> function handle(r)
>> local host = r.headers_in['host']
>> r:puts(host)
>>
>>
Thanks, I will poke into it as soon as I have a chance!
On Thu, Feb 5, 2009 at 9:20 AM, Brian Akins wrote:
> Here's a patch just to give you an idea of what I'm thinking. It compiled.
> This is more to get some ideas going to see how/iff this fits into mod_lua.
>
> The biggest issue is that the
Here's a patch just to give you an idea of what I'm thinking. It compiled.
This is more to get some ideas going to see how/iff this fits into mod_lua.
The biggest issue is that the package_paths are per_dir and in post_config,
you can't really get at those in a useful way. I "precompile" all of
On Feb 5, 2009, at 2:36 AM, Plüm, Rüdiger, VF-Group wrote:
The parent process watchdog is supposed to be used only for core
features that affect all children's and can be done without
requiring graceful restart.
Why can these tasks not be performed by a dedicated child?
Making the module ru
I'm hacking on getting the former work I did for mod_wombat to have
per-thread lua states/scopes into mod_lua. I like the new pool approach.
My main reason for this is we have some code that runs on almost every
request that we are careful about variable scope, etc that the overhead of
creating a
> -Ursprüngliche Nachricht-
> Von: Mladen Turk
> Gesendet: Donnerstag, 5. Februar 2009 12:04
> An: dev@httpd.apache.org
> Betreff: Re: new watchdog module
>
> Plüm, Rüdiger, VF-Group wrote:
> >
> >
> >> -Ursprüngliche Nachricht-
> >> Von: Mladen Turk
> >> Gesendet: Donnerst
Shibu Narendranathan wrote:
Hi All,
I am trying to implement a proprietary encryption mechanism on an
existing apache server.
What is desired is the following.
ClientServer
--|-
1) sends a
Hi All,
I am trying to implement a proprietary encryption mechanism on an
existing apache server.
What is desired is the following.
ClientServer
--|-
1) sends a binary message to | 1) receiv
Thankyou Pierre,
I got my example mod working and played around it.
I am learning more.
Thanks a lot again!
Regards,
Shibu.
-Original Message-
From: pierre.h...@mindlab.de [mailto:pierre.h...@mindlab.de]
Sent: Thursday, January 29, 2009 6:02 PM
To: modules-...@httpd.apache.org
Subject:
Plüm, Rüdiger, VF-Group wrote:
-Ursprüngliche Nachricht-
Von: Mladen Turk
Gesendet: Donnerstag, 5. Februar 2009 06:36
An: dev@httpd.apache.org
Betreff: Re: new watchdog module
Ruediger Pluem wrote:
I would like to commit this module to trunk.
It's a watchdog module that creates a
It seems there is a little problem in my code.
When defining "ProxyErrorOverride On" at the vhost level, then
"ProxyErrorOverride Off" at a directory level, the directive does not
seem to work at the directory level.
The merge works correctly, I traced it, and "error_override" is set to 1
at
19 matches
Mail list logo
