CVS update: php31

From: Date: Mon, 09 Nov 1998 19:39:08 +0000
Subject: CVS update: php31
Groups: php.dev 
Request: Send a blank email to php-dev+get-2305@lists.php.net to get a copy of this message
Date: Monday November 9, 1998 @ 14:39 Author: ssb Update of /repository/php31 In directory asf:/u2/tmp/cvs-serv15204 Modified Files: TODO31.txt Log Message: 80 columns Index: php31/TODO31.txt diff -c php31/TODO31.txt:2.1 php31/TODO31.txt:2.2 *** php31/TODO31.txt:2.1 Sun Aug 30 02:45:14 1998 --- php31/TODO31.txt Mon Nov 9 14:39:07 1998 *************** *** 1,4 **** ! $Id: TODO31.txt,v 2.1 1998/08/30 06:45:14 shane Exp $ +---- | * -- to be done --- 1,4 ---- ! $Id: TODO31.txt,v 2.2 1998/11/09 19:39:07 ssb Exp $ +---- | * -- to be done *************** *** 19,47 **** Core Functions -------------- ! P Identify and move all server-specific code out of the core of php and into the ! SAPI structures. ! * make the config parser able to read more than one ini file per request. Then I can ! implement per-directory directives for iis and any other windows server that doesnt ! have all the nice apache stuff. ! (perhapes handle this differently) Thread Issues ------------- ! * figure out where the hell that one single character outputed at the very end comes from. ! It realy sticks out in the thread version, but see it on rare occasion in 3.0 also. ! U YY_TLS_VARS in main() causes an access violation. Doesnt appear to do this in the flex ! scanner though. (Was uninitialized threads. shane) ! V we have to make a master list and a request list of dl's that are loaded. The current ! implementation relies on a request (thread) always being there, which with threads is ! not true. Probably need to make the dl list true global, and use critical sections around ! the dl functions. Currently, an access violation occures in request shutdown in the ! _php3_hash_apply function that does the module registry cleanup. ! V for isapi, all headers must be sent in one call (including cookies). Nees to pool all ! headers together, then call sapi->header when ready to send header. ! U fix php3_ini_master -> php3_ini so that the copy is done per request and the master ! is a true global. ! P create a debug messages in critical thread areas for debug version compiles Extensions ---------- --- 19,53 ---- Core Functions -------------- ! P Identify and move all server-specific code out of the core of php ! and into the SAPI structures. ! * make the config parser able to read more than one ini file per ! request. Then I can implement per-directory directives for iis and ! any other windows server that doesnt have all the nice apache stuff. ! (perhapes handle this differently) Thread Issues ------------- ! * figure out where the hell that one single character outputed at the ! very end comes from. It realy sticks out in the thread version, but ! see it on rare occasion in 3.0 also. ! U YY_TLS_VARS in main() causes an access violation. Doesnt appear to ! do this in the flex scanner though. (Was uninitialized threads. ! shane) ! V we have to make a master list and a request list of dl's that are ! loaded. The current implementation relies on a request (thread) ! always being there, which with threads is not true. Probably need ! to make the dl list true global, and use critical sections around ! the dl functions. Currently, an access violation occures in request ! shutdown in the _php3_hash_apply function that does the module ! registry cleanup. ! V for isapi, all headers must be sent in one call (including cookies). ! Nees to pool all headers together, then call sapi->header when ready ! to send header. ! U fix php3_ini_master -> php3_ini so that the copy is done per request ! and the master is a true global. ! P create a debug messages in critical thread areas for debug version ! compiles Extensions ---------- *************** *** 72,78 **** Miscellaneous ------------- ! D Consider usage of new api's and libraries such as the Netscape library for cross-platfrom ! functions. They also have a messageing library which includes pop and imap support, is ! it thread safe? (probably) We should move to that rather than the non-thread safe umich library. (3.2) --- 78,85 ---- Miscellaneous ------------- ! D Consider usage of new api's and libraries such as the Netscape ! library for cross-platfrom functions. They also have a messageing ! library which includes pop and imap support, is it thread safe? ! (probably) We should move to that rather than the non-thread safe umich library. (3.2) -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net

« previous php.dev (#2305) next »