Per Einar Ellefsen wrote:
Please be careful not to overdo here, the size does matter, the other way around.
I'll try and do my best, and take another stab at this. I don't however want to make things overly simplified: some things should be ok for newbies, but some other things are more oriented towards the experienced web programmer. For example, to understand "Sessions" you have to have some experience: my example was more directed to Java/PHP programmers having used sessions before, and might be amazed about how easy it is with mod_perl.
I disagree with you, we will end up creating another set of docs. Be prepared to answer numerous questions regarding this section. I don't think that was the idea. This is "What's mod_perl", a teaser. For complete docs we have docs.
Well, they'll have to learn Perl anyway. The ASP example wasn't complicated at all, anyone with 2 minutes programmng experience would understand it. I'll extend more on comments as I said above though. For the Embperl one, I'll make it easier, removing the DB stuff (the table things is most interesting). As for AxKit, there wasn't even any Perl in it! XML is the hit of the year, so let's try and drag people into it!
I beg your pardon, let's *not* try and drag people into hyped things. It's a known thing that I have a very ill attitude towards xml, but my point is: if there was no perl in in what is it doing in the section called "What is mod_perl?"
Stop for a moment throwing everything in one pile. Ask yourself "What is mod_perl?", asnwer it and you will see that many of the things you've added are *not* mod_perl. They are things running on top of mod_perl.
mod_perl is:
* Apache API * Registry * <Perl> sections * Persistent database * Shared memory * threads (2.0)
mod_perl is not: * Application Frameworks (Axkit, ASP, ...)
I think it's better to just say that the feature is available with a link to a proper doc, rather just making the person go confused.
* Apache 2.0 support
I doubt this is a good title. Of course we support Apache 2.0. This is not a feature, this is *the* thing. Remember that after awhile 2.0 will be *the* version, so it'd be silly to advertise it as a feature. moreover currently 2.0 support is alpha-beta yet.
i suggest to rename it. "Apache 2.0's new features support"
Ok. But anyway, once mod_perl 2.0 comes into General Availability (or whatever we call it), this doc will have to be changed. For now, mod_perl 1.0 is the king, and mod_perl 2.0 is something people might want to have fun with.
Fun? You are mistaken again. This section is for *newbies* not for those who use mod_perl for years and looking for that kind of fun.
Imagine a new person coming to us and we give him this fun. I doubt this person will stay with us. If you want to give fun, give them something that works and something that they will have very little frustration with.
This doc isn't a "working examples" page. It's supposed to show basic syntax and how *easy* things are. Writing a protocol server with mod_perl looks *easy* with Apache::Echo.
Sure, wait till 2.0 is released and then have a section on protocols and filters.
Do you have any other ideas for the Apache 2.0 page?
there shouldn't be 2.0 page. 2.0 is not out yet. Let's not following marketing strategies on this one. Once it's out and there are solid docs for it a teaser with a link to those docs is perfect.
BTW, I think once 2.0 is out the features should be added on their own. Once you said 'mod_perl is Apache API' you said it all.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
