Changeset 153 for trunk/doc/devel/TODO
- Timestamp:
- 06/02/09 18:28:07 (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/devel/TODO
r140 r153 11 11 paths. Reglookup should take the user path and unquote each path 12 12 component using the \xQQ syntax prior to searching. 13 14 - It might be nice to have a way to filter results by security 15 descriptor information. Maybe by MTIME as well. 13 16 14 17 - Testing, testing, and more testing. reglookup needs to be tested on … … 26 29 27 30 - Unicode support still needs improvement. While parsing strings seems 28 to be decent, UTF-8 output would be nice. 31 to be decent, UTF-8 output would be nice. Need support for 32 UTF-16LE key and value names. To do this, the UTF conversion 33 functions need to be moved to regfi. 29 34 30 35 - The interface between reglookup.c and regfi.c is much better than it … … 35 40 library. 36 41 37 - NK/VK/SK record caching. Right now, HBIN metadata and SK records are 38 cached, but it's pretty haphazard, and NK/VK records are repeatedly 39 re-parsed. A generic caching library has been introduced but needs to 40 be applied to NK records at a minimum. Eventually, VK records and 41 data should also be cached separately and only be parsed when needed, 42 rather than when a key is loaded up front. Caching also needs 43 configurable object limits, preferrably configurable at build-time. 44 45 - It might be nice to have a way to filter results by security 46 descriptor information. Maybe by MTIME as well. 42 - Develop and solidify regfi API. Regfi should be better documented and 43 eventually needs a set of Python wrappers. 47 44 48 45 - Documentation. The security descriptor output format needs to be … … 58 55 dictate which version of conversion function is used. 59 56 60 - It appears the registry may actually support UTF-16LE names on keys,61 if the key type field is set appropriately. Once data parsing is62 integrated into regfi, then the UTF-16LE handling routines (which63 would then be built-in) should be used to properly handle this case.64 65 57 - Grep through the source for 'XXX', and you'll find more.
Note: See TracChangeset
for help on using the changeset viewer.