> What is missing or too hard to do in mod_perl? 1) Using an MPM other than prefork 2) Websockets
On Tue, Mar 23, 2021 at 2:57 PM Chris <cpb_mod_p...@bennettconstruction.us> wrote: > On Wed, Mar 17, 2021 at 08:40:33PM +0100, Sander Striker wrote: > > Dear community members, > > > > As projects mature, they will naturally reach a point where activity > > reduces to a level such that the project is no longer sustainable. At > > Apache, projects reach this stage when there are not at least 3 active > PMC > > members providing oversight. Projects that reach this stage are usually > > placed in the Attic [1] or absorbed by another Apache project willing to > > manage its releases. > > > > I don't know that I would be good as a PMC. But I do want mod_perl to > continue. > > I do have some general questions for everyone. > > Other than maintaining and security updates, what does everything think > about the following issues: > > What is missing or too hard to do in mod_perl? > Some of this could be very easy or very hard to code. > Maybe just some small fix no one ever did or finished. > > What is missing in documentation? > The website isn't very good. The man pages are decent. > Example code is pretty much non-existent. > Putting tons of examples in man pages, IMHO, is a bad idea. > But by not having any examples across the board, mod_perl is very > difficult for new users to grasp in it's full depths. Which is where all > of the goodies are at. Alternatives to mod_perl are just as good if you > can't fully reach into it completely. > > I'm actually pretty passionate about this. > I realize that there is a lot of proprietary code out there that cannot > be directly released, but the different tasks that are solved ought to > be OK to talk about. > Then, some solutions could be posted to the list and/or elsewhere. > > Small, medium and large websites are three different kinds of problems. > Some needs are identical, but very different as far as volume. > Independent developers working for companies by contract also exist. > > I'm willing to put in plenty of work on this. I'll learn tons of new > things and that means I'll be able to do many things better. > I think that making the effort of learning mod_perl a breeze is probably > the best form of advocacy. > > I don't see myself as being able to do any coding in the guts of > mod_perl. > > > What other things need doing? Coding, basic documentation, and a fuller > documentation that teaches mod_perl beyond the throw in your old cgi code. > > If anyone wants to talk about some serious documentation efforts, let's > start a new thread. > > Thanks, > Chris > > > -- John Dunlap *CTO | Lariat * *Direct:* *j...@lariat.co <j...@lariat.co>* *Customer Service:* 877.268.6667 supp...@lariat.co
