Per Einar Ellefsen wrote:I have added sections below "Configure Apache with Perl" (the more >> documents).
got it:
* The first example is the code but no config. Are those examples intented to be just a teaser or fully functional? If the latter we need to add a sample config section.
Well, I was only intending it as a teaser, because I don't want to go creating a complete application using sessions. That handler doesn't do anything, it just shows how easy it is to get session info and use it.
* The same here:
start/tips/app-servers.html
it's good for slides, but not enough padding for a document. The start is great, but I believe huge snippets of code without explanation are bad, unless you use it as a teaser and look-n-feel demo.
Once again, I don't want to being explanation. The point is just to show example syntax, which some PHP/ASP/anything-junkies might love. Explanation is good for docs, this is mostly to attract people. Of course I could add a sentence or 2, but I don't want more than that.
* 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.
as for the "more", there are *many* new features. i'm working on this doc, hopefully will release it soon, so I'm not sure whether using something that's far from incomplete is good.
Again, major changes will come with mod_perl 2.0 stable releases.
* Also probably a good idea to add "World Wide acceptance" or something like that with links to /outstanding
Good idea.
* Another issue is that while many people come to mod_perl via the registry family, this is not the feature that should come up first,
"Easily create custom modules that become part of Apache" "Gain access to all request stages"
should probably come before registry.
True, but as an eye-catcher, the first point would be "Faster CGI" as something people unfamiliar with these whole handler-thingies would tick on. For me, this page isn't anything else than advertising: we're trying to catch programmers and managers alike, and it's most likely they are already running CGI which they want a replacement for.
By the way: src/start/tips/logging.pod isn't used. Should we maybe delete it?
May be we can use it, e.g. using Apache::STRLog or what was the name of this module people are always looking for? I think it was in the eagle book or something like that.
? We could add it to the favicon example.
probably not a good idea to make things look more complicated, remember this is for first time users.
Ok, we drop it then...?
-- Per Einar Ellefsen [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
