You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Manoj Kasichainula <ma...@io.com> on 2000/01/04 21:58:57 UTC

Re: cvs commit: apache-2.0/src/modules/standard mod_digest.c mod_vhost_alias.c

On Fri, Dec 31, 1999 at 05:46:08PM +0000, Ben Laurie wrote:
> On that note ... how do you actually get a module into Apache 2.0? I
> tried to add mod_actions earlier today (./configure --enable-actions)
> but it didn't seem to result in a server that understood Action.

Hmm, weird. When you --enable-action, it should result in a new
modules.c being generated, and mod_action.c being compiled into the
server. Is there anything else that should be done that I missed? Are
one of these two steps not happening?

> Not sure I'm keen on that method of doing it, anyway.

What do you suggest?


Re: cvs commit: apache-2.0/src/modules/standard mod_digest.c mod_vhost_alias.c

Posted by Manoj Kasichainula <ma...@io.com>.
On Tue, Jan 04, 2000 at 10:19:03PM +0000, Ben Laurie wrote:
> I'm not sure what's missing - certainly configure said it was adding
> actions. If it is expected to work, I'll look harder. Have you tried it?

All I've tested is that the server doesn't crash and die when those
modules are compiled, in; I haven't tested the actual functionality of
those modules yet. I can't think of a reason it wouldn't work though.

> Well, I still like the Configuration file (only for specifying
> modules'n'stuff) - having a command line a zillion miles long instead
> seems like a poor deal.

I think it would be easy enough to make the configure script load a
list of configuration values. We just make each check for --enable or
--with blah also look at the loaded config value for that
configuration parameter.


Re: cvs commit: apache-2.0/src/modules/standard mod_digest.c mod_vhost_alias.c

Posted by Ben Laurie <be...@algroup.co.uk>.
Manoj Kasichainula wrote:
> 
> On Fri, Dec 31, 1999 at 05:46:08PM +0000, Ben Laurie wrote:
> > On that note ... how do you actually get a module into Apache 2.0? I
> > tried to add mod_actions earlier today (./configure --enable-actions)
> > but it didn't seem to result in a server that understood Action.
> 
> Hmm, weird. When you --enable-action, it should result in a new
> modules.c being generated, and mod_action.c being compiled into the
> server. Is there anything else that should be done that I missed? Are
> one of these two steps not happening?

I'm not sure what's missing - certainly configure said it was adding
actions. If it is expected to work, I'll look harder. Have you tried it?

> > Not sure I'm keen on that method of doing it, anyway.
> 
> What do you suggest?

Well, I still like the Configuration file (only for specifying
modules'n'stuff) - having a command line a zillion miles long instead
seems like a poor deal.

Cheers,

Ben.

--
SECURE HOSTING AT THE BUNKER! http://www.thebunker.net/hosting.htm

http://www.apache-ssl.org/ben.html

"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi