Re: apache.make

[Helge Hess]

Nicola Pero wrote:
> Ahm - I think this is a good suggestion for what can be improved - not
> directly applicable, but that's my fault - probably I didn't explain
> myself enough.

No, the issue is quite clear to me.

> This stuff is quite different from the Apache adaptor in GSWeb.

Yep, though the GSWeb adaptor could be written as an ObjC Apache module.

> apache.make can be used to build Apache modules which contain Objective-C
> code and are linked against the GNUstep libraries. (Unlike the Apache
> adaptor in GSWeb which is written in pure C).

Exactly.

> To load these Apache modules, the dynamic linker needs to find the GNUstep
> shared libraries !

Yep.

> Possibly the simplest solution is going to be something like
> opentool /opt/apache/bin/apachectl start

No, as I said this is IMHO not acceptable. Apache should be started as
is and configuration should be handled by the Apache GNUstep module.
Of course this configuration module is not allowed to link GNUstep
libraries yet for obvious reasons.

I think about something which is like the mod_env module, only
specialized for the GNUstep environment and affecting the current Apache
process.

The sequence in httpd.conf could look like:
---snip---
LoadModule gsenv_module     // load GNUstep config
GNUstep_configure /GNUstep  // set GS environment in Apache process

LoadModule mytest_module    // load an Objective-C module
<LocationMatch "^/MyTest*">
SetHandler mytest-handler   // address ObjC handler
</LocationMatch>
---snap---

BTW: it would be even cooler, if each Apache ObjC module would be a
bundle which has an appropriate Apache principal class.

Helge
-- 
SKYRIX Software AG - http://www.skyrix.com