woo hoo. good news indeed. a maintainer is just what is needed.

i'm pretty sure Maypole will work with apache2 as a mod_fastcgi script. i know it works fine that way on apache1. the fastcgi FAQ and examples have the code, it's only a few lines added into CGI::Maypole to make a FCGI::Maypole.

it's also easy enough to get around the Apache::* dependencies, i believe A::Request is just used for Cookies.

imho, the Apache::* dependencies should be removed as they are mod_perl related and not merely for apache. i hacked my FCGI Maypole enough to support Cookies and Sessions using the same interface that the Maypole modules use (Maypole::UserSessionCookie or somesuch) but just using the functions provided by CGI::Simple. just a little work would let Maypole support request headers without relying on A::Request.

i have patches for most of these things, but since nobody was maintaining i didn't send them in. the original project i chose Maypole for is about ready for it's second incarnation and i've been wondering if i should continue with Maypole or try another path.

i'm on the mailing lists, i'll pay attention now that there's somebody at the helm and i hope Maypole picks up some momentum.

It would be nice if someone started a patches section on th e Maypole wiki to keep that kind of stuff on. It would be an easy way for you to show your patches and hopefully get them worked into development. Just my 2 cents! :)


___________
Eric Hodges

Thats what the mailing lists are for! ;)

Please note that the wiki URL in this node is no longer operational.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds