Mango, DSource, and CGIHTML

[Pragma]

Morgan McDermott wrote:
>  Hmm.. The CGIHTML port would be a quick-and-easy solution for me right 
> now, so I may go in that direction, but I've been considering writing an 
> Apache module for a while. I have the one book I can find on the subject 
>  (O'Reilly's Writing Apache Modules with Perl and C), and I might turn 
> to that solution simply because I was planning to use Apache for this 
> project anyway, and Apache has neat features to hook into [ storing 
> state information in web-server memory, etc].

An apache module for D would be very nice to have.

I made a stab at writing one about 1.5 years ago, to support DSP when it 
was in its infancy.  The major problem I ran into was that the Apache 
bindings, as provided, are encrusted with #define statements that are 
used to build your module - they pretty much assume you're using GCC, 
and little else.

You're also right about Apache's resource management.  It has all kinds 
of goodies, including memory pools for pseudo-GC-style coding.  I have 
no clue how exploitable all those bells-and-whistles are, as I never 
made it that far.

That said, a lot has changed in that amount of time.  Probably crafting 
a C-to-D bridge would probably do wonders for this.  The source for 
mod_python is another possible place to hack around, aside from mod_perl.

Good luck!

-- 
- EricAnderton at yahoo