Home / Got mod_perl? / | ||||
Known advocacy issues | ||||
|
||
This document keeps track of issues brought up on the mod_perl Advocacy mailing-list. It serves as a repository of things people volunteered to do, good ideas missing a volunteer, and overall strategies towards world domination.
If you want to become a part of the effort, make sure to join the list!
How can we make it even easier and smoother for newbies to introduce themselves with mod_perl ?
It was suggested that we have a better quick start guide for new users with stub handlers, stub apache configs, etc. Maybe have a "run in place" installation for people to try mod_perl.
Ideas and tasks to increase the overall availability of mod_perl at ISPs and hosting providers
It is difficult to find mod_perl friendly hosting providers. Except full hosted server or User Mode Linux which still means they have to maintain an entire server. Should we maybe have a "How to be a mod_perl web host provider?" HOWTO?
Ideas for possible articles and existing articles awaiting publication
Demonstrate the ability to write protocol handlers in mp2 by creating a server that speaks something other than HTTP. The only trouble is, I'm having a hard time coming up with a scenario where I would really advise using a different protocol...
Build a better DBD::Proxy by making it use XML-RPC or SOAP (or teach mp2 to speak PlRPC with a protocol handler!) and talk to an Apache::DBI-enabled server. This should be much faster than the current system which doesn't use persistent connections, and would allow all the standard apache logging and access control stuff to be used.
Use an mp2 filter to do something that would have been impossible before, like efficiently post-processing a PHP script (which also demonstrates that PHP has no access to the apache API).
Use an mp2 filter to apply an XSL transform to some XML content.
Use an mp2 filter to automate some of the cache control suggestions from Michael Radwin's OSCON talk: http://public.yahoo.com/~radwin/talks/http-caching.htm
Use an mp2 filter to implement cookie-less sessions by rewriting URLs and adding hidden fields to forms.
Write a handler that fetches content from CVS or Subversion, with the branch to use being set by a cookie or URL param or virtualhost name. This would be for content people working on version-controlled websites to use.
Has an article about a client's conversion to mod_perl, thinking about submitting to Linux Journal and/or Dr. Dobbs.
Volunteered to interview TicketMaster employees for his column.
Has written articles mentioning mod_perl:
http://www.stonehenge.com/merlyn/LinuxMag/col03.html
http://www.stonehenge.com/merlyn/LinuxMag/col17.html
http://www.stonehenge.com/merlyn/LinuxMag/col26.html
http://www.stonehenge.com/merlyn/LinuxMag/col28.html
http://www.stonehenge.com/merlyn/LinuxMag/col33.html
http://www.stonehenge.com/merlyn/LinuxMag/col36.html
http://www.stonehenge.com/merlyn/LinuxMag/col60.html
http://www.stonehenge.com/merlyn/LinuxMag/col61.html
http://www.stonehenge.com/merlyn/WebTechniques/col18.html
http://www.stonehenge.com/merlyn/WebTechniques/col24.html
http://www.stonehenge.com/merlyn/WebTechniques/col32.html
http://www.stonehenge.com/merlyn/WebTechniques/col41.html
http://www.stonehenge.com/merlyn/WebTechniques/col47.html
http://www.stonehenge.com/merlyn/WebTechniques/col48.html
http://www.stonehenge.com/merlyn/WebTechniques/col49.html
http://www.stonehenge.com/merlyn/WebTechniques/col50.html
http://www.stonehenge.com/merlyn/WebTechniques/col54.html
http://www.stonehenge.com/merlyn/WebTechniques/col55.html
http://www.stonehenge.com/merlyn/WebTechniques/col57.html
http://www.stonehenge.com/merlyn/WebTechniques/col58.html
http://www.stonehenge.com/merlyn/WebTechniques/col59wt.html
Wrote an article on mod_perl 2.0 for SysAdmin Magazine.
http://www.revsys.com/writings/modperl.html
Maintain a constantly changing and up to date "What's new" section on the front page of the perl.apache.org site. Design in a way that is as automatic as possible, and allow a wide group of mod_perl people to contribute snippets of news. Important to make sure that expired news vanish and do not go stale.
Owner: perrin
Reference: http://www.mail-archive.com/advocacy@perl.apache.org/msg00053.html
The last mod_perl digest was published on 2003/10/20 by James Smith. Consider reviving it and/or tying it to the news portion of the site
A few non technical publications were suggested as good possible targets for mod_perl advocacy. In no particular order :
There are tons of modules and applications built on top of mod_perl. It is important to track down the biggest, most used application's compatibility and support under mod_perl 2.0 series.
Supported, possibly replaced by DBI::Pool
David Wheeler is helping in making sure version 3.0 is mod_perl 2.0 ready
Need more numbers to show people in the press releases such as number of sites, book sales, etc.
Why not coordinate and make efforts to have frequent mod_perl stories cross-posted on slashdot ?
How come mod_perl doesn't have it's own slashdot category icon yet ?
Is there even a mod_perl project categorized on freshmeat ? Is it kept in sync with releases ?
X-Powered-By : mod_perl/2.0
In many cases, servers are hidden behind proxies and don't reveal full server-tokens thru the Server: header. PHP has been using the X-Powered-By header for a long time. Isn't it about time for mod_perl to self-publicize in the same way ?
Owner: gozer
What kind of help can we get out of them ? We need somebody to be the point person for interactions with them.
What kind of help can we get out of them ? We need somebody to be the point person for interactions with them.
Jeff Bisbee talked to Gavin Estey (Perl Foundation PR Chair) and the latter agreed to help.
This is a list of success stories that should be worth chasing after. We need to get the successful users of mod_perl to speak up.
Getting a success story from Weta (Lord of the Rings)
Contact: Milton Ngan, <milton (at) wetafx.co.uk>
Owner: gozer
They have migrate from Java to mod_perl. Great potential success story along with what they gained from switching to mod_perl. A considerable amount of time and effort must have been spent evaluating possible alternatives.
The maintainer is the person you should contact with updates, corrections and patches.
Philippe M. Chiasson <gozer (at) apache.org>
|