I was also thinking that it'd be nice to cut the pod files from A-T's .pm files, just like we do with mod_perl. Host those in the modperl-docs repository and extract those via svn into Apache-Test/docs/ which consequently gets glued to .pm files on install. That way online docs will be complete.

In which case it probably makes sense to follow the same layout as mp docs, i.e.:

Apache-Test/api/  <= Apache::Test, Apache::TestRequest, etc.
Apache-Test/user/ <= tutorials and stuff

The user/ will probably split into perl/, php/, python/, etc, with language specific docs living under those dirs.

I suppose that the client side will be always be in perl, right?

so may be it should be /server/ instead of /user/?

Apache-Test/api/         <= Apache::Test, Apache::TestRequest, etc.
           /client/      <= client stuff
           /server/perl/ <= tutorials and stuff
                  /php/
                  /python/




-- __________________________________________________________________ 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

Reply via email to