--- loncom/TODO 2001/11/28 21:51:18 1.140 +++ loncom/TODO 2001/11/28 22:00:07 1.143 @@ -5,14 +5,16 @@ TODO list * bug ! Priority ? Questionable/unverified -c Continual +c Continual and currently in an okay status +C Continual and in need of a lot of work right now G=Gerd A=Alex S=Scott Y=Guy N=Hon-Kie -I=Issac +I=Isaac +M=Matthew ?=not yet assigned XMLPARSE @@ -114,7 +116,6 @@ SYSTEM MONITORING & improve output of 'make status(post)' target in loncom/build (S) BUILD - * make sure that ssh is always allowed, even for run-time servers (S) c test code... up to date with latest CPAN modules (S) + allow for debian and redhat 7.1 installation... redhat 7.1 installation well pioneered (S) @@ -123,12 +124,12 @@ BUILD c document and reasonably automate aspects of source-to-build procedure (S) CODE QUALITY - c code lines less than 80 characters (somewhat done, but now put + C code lines less than 80 characters (somewhat done, but now put on back-burner till 2002) (S) - c xhtml-ize output from perl modules (S) - c work on javascript library and modularizing code (S) + C xhtml-ize output from perl modules (S) + C work on javascript library and modularizing code (S) & fix handling of web browser windows (S) - c add in CPAN and POD conventions into modules and scripts (S) + C add in CPAN and POD conventions into modules and scripts (S) SQL DATABASE + have result capping (S) @@ -137,7 +138,7 @@ SQL DATABASE & restrict search fields to viewable fields (based on ENV{user.adv}) (S) & update user-viewable metadata database documentation (S) & restrict searching to browseable domain (S) - c monitor speed and performance of metadata database (S) + C monitor speed and performance of metadata database (S) + prepare for and upgrade to the much superior MySQL version 4 (S) PUBLISHING 500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.