You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axkit-dev@xml.apache.org by da...@apache.org on 2002/02/01 16:34:37 UTC
cvs commit: xml-axkit TODO
darobin 02/02/01 07:34:37
Modified: . TODO
Log:
Added a few TODO items, will add more
Revision Changes Path
1.2 +32 -0 xml-axkit/TODO
Index: TODO
===================================================================
RCS file: /home/cvs/xml-axkit/TODO,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- TODO 13 Jan 2002 20:45:08 -0000 1.1
+++ TODO 1 Feb 2002 15:34:37 -0000 1.2
@@ -0,0 +1,32 @@
+
+This is the TODO file for AxKit. Thank you for wanting to contribute! The
+first thing you probably want to do if you haven't already is to check out
+the xml-axkit module from the cvs.apache.org CVS in order to get the latest
+code, and to read the CONTRIB file.
+
+
+ . Eliminate dependency on Apache / mod_perl
+
+ This is a rather large undertaking. It is not technically hard though.
+ The current AxKit relies heavily on Apache and mod_perl, which means that
+ it can't be used as a generic publishing system or as a CGI module. The
+ Apache handler that drives the code needs to be abstracted away so that
+ AxKit can be driven by any kind of request, the Configuration needs to
+ have an alternate format to work outside of Apache, Apache::Fake needs to
+ be used to emulate $r and other such things.
+
+ . Documentation
+
+ This is the job of the axkit-docs project. It really needs to be done and
+ can use all the help that it gets. This would be a nice way to learn
+ AxKit's internals if you are not familiar with them. Ask the
+ axkit-docs@axkit.org list.
+
+ . Splitting XSP out
+
+ Currently XSP is tied into AxKit but it would make a marvellous
+ standalone module for XML processing.
+
+
+
+