On Sun, 2002-04-21 at 17:44, Dave Rogers wrote:
> I have the need to use mod_webkit with Apache 2.0.35.
> Has anyone compiled this to work with Apache 2.0.35?
> If so, where can I get it?
> I was using Apache 1.3.24 but had trouble with SSL under windows. I could only get SSL working with 2.0.35.
> If its not compiled for Apache 2.0 yet, how serious of an undertaking would it be to compile it for Apache 2.0?
Extensive changes were made to the server API in Apache 2.0. Existing
modules designed for the Apache 1.3 API will not work in Apache 2.0
without modification. Details are provided in the developer
Since mod_webkit is a quite simple as modules go, it should not be as
horrendous as this page suggests, but if IIRC, from my own unfinished
attempt to port it, it is not trivial. Memory management was the first
thing I was dealing with. The other thing I ran across is that
mod_webkit itself was patched together from various places. Being the
perfectionist/optimist I was then, I started a clean rewrite rather than
a straightforward port. Perhaps that explains why it was never
However, now that 2.0 is the official stable release of apache, and
since this question gets asked approximately biweekly on the webware
lists, I believe the time has come to take the plunge.
Any takers? I am willing to do it, but it probably will be another
month before I get a serious start.
Another option, probably easier in both the short run and the long run,
is to find another similar module like mod_backhand that has already
been ported, and write another adapter to connect to it:
let someone else maintain the icky C part,
write the adapter in clean, sweet, elegant Python! 8-)
may be a little more work dealing with non-webware specific
stuff. (e.g. parsing the stream instead of marshal.loads())
Any comments on this approach? Jay? (I imagine there was a reason you
wrote mod_webkit in the first place, instead of using mod_backhand.)