diff options
author | wrowe <wrowe@13f79535-47bb-0310-9956-ffa450edef68> | 2007-11-05 22:57:32 +0000 |
---|---|---|
committer | wrowe <wrowe@13f79535-47bb-0310-9956-ffa450edef68> | 2007-11-05 22:57:32 +0000 |
commit | 6030c214f7aa347259962fc46ce389bd7963fe57 (patch) | |
tree | 31e7167644658f61cb32d026c9648f0e7827b0aa /STATUS | |
parent | b410db4509cc0b06bad0b57f6e987129f9cd926e (diff) | |
download | libapr-6030c214f7aa347259962fc46ce389bd7963fe57.tar.gz |
trunk/STATUS is our official home for such things
git-svn-id: http://svn.apache.org/repos/asf/apr/apr/branches/0.9.x@592177 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'STATUS')
-rw-r--r-- | STATUS | 375 |
1 files changed, 4 insertions, 371 deletions
@@ -36,43 +36,11 @@ Release: RELEASE 0.9 SHOWSTOPPERS: -RELEASE 1.0 SHOWSTOPPERS: - - * Must namespace protect all include/apr_foo.h headers. Jon Travis - has especially observed these including apr within Apache-1.3. - Message-ID: <20020128100116.A4288@covalent.net> - Deprecating the symbols in 0.9, eliminating them with 1.0. - (Those problems have been fixed, but it is a good example of - what to look for.) - Some headers with issues: - apr.hnw (READDIR_IS_THREAD_SAFE, ENUM_BITFIELD, - _POSIX_THREAD_SAFE_FUNCTIONS (?)) - apr.hw (NO_USE_SIGACTION) - - - * Flush out the test suite and make sure it passes on all platforms. - We currently have about 450 functions in APR and 147 tests. That - means we have a large number of functions that we can't verify are - actually portable. This TODO includes finishing the migration to the - unified test suite, and adding more tests to make the suite - comprehensive. - - * close out the XXX's already! (wrowe: this is "production release" - quality code with that many unanswered questions?) If they aren't - showstoppers, deprecate them to TODO:s. - - * complete the efforts started by DougM for cleaner fn naming - conventions: see proposed name changes in renames_pending - and offer up any additions/vetos/clarifications. - DougM offered to complete the work with his nifty perl rename - script at the hackathon. - Thom says: I think this is close to done; does anyone want to add any - further renames? - CURRENT VOTES: + CURRENT test/testall -v EXCEPTIONS: Please add any platform anomilies to the following exception list. @@ -94,341 +62,6 @@ CURRENT test/testall -v EXCEPTIONS: Users: username: Groups from apr_uid_get not implemented -RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: - - * Someone needs to port testucs to Unix. Right now it only works - on Windows. - - * The return type of a thread function (void *) is inconsistent with - the type used in apr_thread_exit()/apr_thread_join() (apr_status_t). - The thread function's return type should be changed to apr_status_t - so that a return from the thread main function has the same effect - as apr_thread_exit(). - See Message-Id: <E16JjZA-0007hg-00@zakath.apana.org.au> for thread - discussing this. - +1: BrianH, Aaron - - * Need some architecture/OS specific versions of the atomic operations. - progress: generic, solaris Sparc, FreeBSD5, linux, and OS/390 done - need: AIX, AS400, HPUX - - * The new lock API is a full replacement for the old API, but is - not yet complete on all platforms. Components that are incomplete - or missing include: - Netware: apr_proc_mutex_*() (Is proc_mutex unnecessary on Netware?) - * proc_mutex is not necessary on NetWare since the OS does - not support processes. The proc_mutex APIs actually - redirect to the thread_mutex APIs. (bnicholes) - OS/2: apr_thread_cond_*(), apr_proc_mutex_*() - - Less critical components that we may wish to add at some point: - Beos: apr_thread_rwlock_try*lock() - apr_proc_mutex_trylock() - Unix: apr_thread_rwlock_*() for platforms w/o rwlocks in pthread - Win32: apr_thread_cond_timedwait(), apr_proc_mutex_*() - (Is proc_mutex unnecessary on Win32?) - - * Need to contemplate apr_strftime... platforms vary. OtherBill - suggested this solution (but has no time to implement): - Document our list of 'supported' escapes. - Run some autoconf/m4 magic against the complete list we support. - Move the strftime re-implementation from time/win32 to time/unix. - Add some APR_HAVE_STRFTIME magic to use the system fn, or fail - over to time/unix/strftime.c. - Message-ID: <025e01c1a891$bf41f660$94c0b0d0@v505> - - * Using reentrant libraries with non-threaded APR - - Anecdotal evidence exists that suggests it is bad to - mix reentrant and non-reentrant libraries and therefore - we should always use the reentrant versions. - - Unfortunately, on some platforms (AIX 4.2.1) defining - the reentrant flag (-D_THREAD_SAFE) causes builds to fail, - and so one would expect --disable-threads to fix this. - Although this has been fixed for that particular version - of AIX, it may be useful to only enable the reentrant - versions when threads are enabled. - How will we deal with this issue once APR becomes a standalone - library? It is perfectly legitimate to have apps needing - both versions (threaded/reentrant and non-threaded/non-reentrant) - on the same machine. - - * Pools debugging - - Find a way to do check if a pool is used in multiple - threads, while the creation flags say it isn't. IOW, - when the pool was created with APR_POOL_FNEWALLOCATOR, - but without APR_POOL_FLOCK. - Currently, no matter what the creation flags say, we always - create a lock. Without it integrity_check() and - apr_pool_num_bytes() blow up (because they traverse pools - child lists that possibly belong to another thread, in - combination with the pool having no lock). However, - this might actually hide problems like creating a child pool - of a pool belonging to another thread. - Maybe a debug function apr_pool_set_owner(apr_thread_t *) in - combination with extra checks in integrity_check() will point - out these problems. apr_pool_set_owner() would need to be called - everytime the owner(the thread the pool is being used in) of - the pool changes. - - - Implement apr_pool_join and apr_pool_lock. Those functions - are noops at the moment. - - - Add stats to the pools code. We already have basic stats - in debug mode. Stats that tell us about wasted memory - in the production code require more thought. - Status: Sander Striker is looking into this (low priority) - - * Deal with largefiles properly on those platforms that support it. - - Justin says: Linux refuses to have sendfile support and largefiles - at the same time. Largefile autoconf patch: - http://www.apache.org/~jerenkrantz/apr_largefile.m4 - - * Get OTHER_CHILD support into Win32 - Status: Bill S. is looking into this - - * Win32 apr_proc_create fails to create 16 bit apps detached - (a win32 bug.) The question - test in advance (slow) or - recover gracefully from failure and try again? Only the test - method will work on Win9x, since it will appear to work, only - to encounter mangled pipes. Win2K (NT?) simply fails. - - * SysV semaphore support isn't usable by Apache when started as - root because we don't have a way to allow the semaphore to be - used by the configured User and Group. Current work-around: - change the initial permissions to 0666. Needed code: See - 1.3's http_main.c, SysV sem flavor of accept_mutex_init(). - Status: Jim will look into this - Update: Apache deals with this itself, though it might be nice - if APR could do something. - - * Build scripts do not recognise AIX 4.2.1 pthreads - Justin says: "Is this still true?" - - * FirstBill says we need a new procattr, APR_CREATE_SUSPENDED (or - something similar) to direct ap_create_process to create the - process suspended. We also need a call to wake up the suspended - process. This may not be able to be implemented everywhere though. - Status: OtherBill asks, why? What is the benefit, how is it - portably implemented? Unless this creates some tangible that - mirrors another platform, then I'm -1. - - * Replace tables with a proper opaque ADT that has pluggable - implementations (including something like the existing data type, - plus hash tables for speed, with options for more later). - Status: fanf is working on this. - - * add a version number to apr_initialize() as an extra failsafe against - (APR) library version skew. - MsgID: <Pine.LNX.4.10.10005231712380.31927-100000@nebula.lyra.org> - Status: Greg -1, Jeff +1, Ryan +1, Tony -0(?), david +1 - - * add apr_crypt() and APR_HAS_CRYPT for apps to determine whether the - crypt() function is available, and a way to call it (whether it is - located in libc, libcrypt, or libufc) - Justin says: Should apr_crypt() be in apr-util? - - Status: Greg +1 (volunteers) - - * configure.in does post-processing on the AC_OUTPUT files (for - VPATH support). This means that config.status doesn't do the - right thing when you re-run it. We ought to revamp the makefiles - to do the right AC_SUBST stuff rather than depend upon rewriting. - - Sascha: As the rewriter is a crude hack, I would not worry too - much about it. It is designed to go away once we have - a proper build system in place. - - One of the perceived deficiencies of automake is that it - uses AC_SUBST too often, thereby slowing down the task of - generating Makefiles significantly, because it applies - dozens of substitutions to each Makefile. And why? Make's - built-in macro processing is much more powerful, and - combined with the include facility, generating Makefiles - becomes simpler and faster. - Justin says: "I think this got fixed with Roy's build changes." - - * use os_(un)cork in network_io/unix/sendrecv.c for FreeBSD's - sendfile implementation. - - david: The socket options stuff is now in and using it should - reduce the number of syscalls that are required for - os_cork and uncork, so the code should be reviewed to - make use of the new calls. If no-one beats me to it I'll - get around to it soonish... - - * toss the per-Makefile setup of INCLUDES; shift to rules.mk.in - rbb: This is a bad thing IMHO. If we do this, then we - can't use these makefiles for anything else. For example, - apr-util - - * add the rest of the pool accessor declare/impl macros. - Justin says: Both thread and file have the accessors now. Any others? - Status: Greg volunteers - - * I think apr_open_stderr() and friends *should* dup() the - descriptor. That would allow the new/returned file to be closed - (via pool cleanup or manually) without accidentally closing - stderr/out. - - * need to export (in code, not just build scripts) the shared - library extension (e.g. ".so") for the platform. clients need to - use this to construct filenames to pass to apr_dso_load() - -- note on Win32 we distinguish 'apache module' names from other - 'loadable module' names, so be careful with Apache's directive. - - * Possible gmtime_r replacement in explode_time - On Solaris (and possibly others), the gmtime_r libc function obtains - a mutex. We have seen 21/25 threads being blocked in this mutex on - a threaded httpd MPM when requesting static pages. It may be worth - it to hand optimize this since there is no real need for a mutex at - the system level (straight arithmetic from what I can tell). If you - have access to the Solaris source code: - osnet_volume/usr/src/lib/libc/port/gen/time_comm.c. - - * Add a way to query APR for what features it has at runtime (i.e. - threads). - Justin says: I'm not completely sold on this, but it has been mentioned - before and at least added to STATUS. - - * apr_xlate.h generates a bunch of compiler warnings. - Jeff asks: which platform? - Justin says: Solaris with Forte 6.1. - - * fcntl() oddness on Solaris. Under high loads, fcntl() decides to - return error code 46 (ENOLCK). - - httpd (prefork MPM) error log says (predictably): - - (46)No record locks available: couldn't grab the accept mutex - - All of the children report this and subsequently exits. httpd is now - hosed. AFAICT, this does not look to be an out-of-fds error. - - Solaris's man page says: - ENOLCK - The cmd argument is F_SETLK, F_SETLK64, F_SETLKW, or - F_SETLKW64 and satisfying the lock or unlock request - would result in the number of locked regions in the - system exceeding a system-imposed limit. - - Justin says: What is this system-imposed limit and how do we change it? - This gives me more rationale for switching the default - interprocess lock mechanism to pthread (if available). - - Explanation (from Kristofer Spinka <kspinka@style.net>): - ============ - The system imposed default limit of outstanding lock requests is - 512. - You can verify this by, in a contemporary version of Solaris: - - # mdb -k - > tune_t_flckrec/D - tune_t_flckrec: - tune_t_flckrec: 512 - - This can be increased by adding the following to /etc/system: - - set tune_t_flckrec=1024 - - and rebooting. - - Of course "1024" can be any reasonable limit, although we do not know - what "reasonable" should be, so be conservative, only increase this as - necessary. - - * Generate a good bug report to send to the FreeBSD hackers that details - the problems we have seen with threads and system calls (specifically - sendfile data is corrupted). From our analysis so far, we don't think - that this is an APR issue, but rather a FreeBSD kernel issue. Our - current solution is to just disable threads across the board on - FreeBSD. - - MsgID: <20010828091959.D17570@ebuilt.com> - Status: Fixed in -CURRENT. MFC in about a week. Continuing - testing with threads on FreeBSD. - - FreeBSD PR kern/32684: - http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/32684 - - * There are some optimizations that can be done to the new - apr_proc_*() functions (on UNIX). One that may reduce pointer - indirection would be to make the apr_proc_mutex_unix_lock_methods_t - first-class members of the apr_proc_mutex_t structure. - - * Condition variables are tricky enough to use, and even trickier - to implement properly. We could really use a better test case - for those subtle quirks that sometimes creep into CV implementations. - - * Once we are fully satisfied with the new lock API, we can - begin to migrate the old API to be implemented on top of the - new one, or just decide to get rid of it altogether. - - * FreeBSD returns 45 (EOPNOTSUPP) when the lockfile is on a NFS - partition when you call fcntl(F_SETLKW). It may be good if we - can somehow detect this and error out when creating the lock - rather than waiting for the error to occur when acquiring lock. - - * Fix autoconf tests for strerror_r on BeOS and remove the hack in - misc/unix/errorcodes.c to get error reporting working. Committed as - the solution is elusive at present. - - * implement APR_PROGRAM_ENV and APR_PROGRAM_PATH on BeOS, OS/2, - Netware, and Win32. - - * stat() on a few platforms (notably Solaris and AIX) succeeds for - a non-directory even if a trailing '/' was specified in the - name. APR should perhaps simulate the normal -1/ENOTDIR - behavior in APR routines which retrieve information about the - file. Note: Win2K fails GetFileAttributesEx in this scenario. - See OtherBill's comments in this message to dev@httpd.apache.org: - Message-Id: <5.1.0.14.2.20020315080852.00bce168@localhost> - -Documentation that needs writing: - - * API documentation - Ian Says: APR Stuff in now in Doxygen format, which is the first step. - - * apr-site needs to be revamped with Anakia/XHTML. - -Stuff waiting for code thawing after Beta 1: - - * Identify and implement those protection bits that have general - usefulness, perhaps hidden, generic read-only [immutable], - effective current user permissions, etc. - - * Maybe make the following functions return void instead of - apr_status_t, as they cannot ever error: - - apr_md5_init() - apr_md5_update() - apr_md5_final() - apr_md5_encode() - apr_md5() /* plus make the obvious code tweak in this one */ - - (Volunteer: Karl Fogel <kfogel@collab.net>.) - - However, don't do this until after apr and apr-util offer - library version numbers, and httpd uses those numbers to - indicate which version it needs. Until the libraries are - versioned, this api change is [somewhat] painful for httpd. - Status: Still in discussion, current leanings appear to be - Bill Stoddard -0.5 (?) - Sander Striker +1 - Greg Stein +1 - Karl Fogel +1 - (Not sure if the negatives would stay negative given that the - change would now wait for the library versioning thing described - above, though.) - Justin says: If you do this, please move it into apr-util where md5 - belongs! You'll have to address the random issue in - misc/unix/getuuid.c that forces md5 to be in APR. - Sander: +1 for the move. - -Stuff for post 1.0: - - * Almost every API in APR depends on pools, but pool semantics - aren't a good match for a lot of applications. We need to find - a way to support alternate allocators polymorphically without - a significant performance penalty. - +SEE svn.apache.org:/repos/asf/apr/apr/trunk/STATUS for all other open +issues to be addressed. [First, patched in trunk; then considered for +backport to the stable branch.] |