Changeset 153 for trunk

Timestamp:

06/02/09 18:28:07 (15 years ago)

Author:

tim

Message:

minor updates to TODO list

File:

• trunk/doc/devel/TODO (modified) (4 diffs)

trunk/doc/devel/TODO

@@ -11 +11 @@
    paths.  Reglookup should take the user path and unquote each path
    component using the \xQQ syntax prior to searching.
+
+ - It might be nice to have a way to filter results by security 
+   descriptor information.  Maybe by MTIME as well.
 
  - Testing, testing, and more testing.  reglookup needs to be tested on 
@@ -26 +29 @@
 
  - Unicode support still needs improvement.  While parsing strings seems
-   to be decent, UTF-8 output would be nice.
+   to be decent, UTF-8 output would be nice.  Need support for
+   UTF-16LE key and value names.  To do this, the UTF conversion
+   functions need to be moved to regfi.
 
  - The interface between reglookup.c and regfi.c is much better than it
@@ -35 +40 @@
    library.
 
- - NK/VK/SK record caching.  Right now, HBIN metadata and SK records are 
-   cached, but it's pretty haphazard, and NK/VK records are repeatedly
-   re-parsed.  A generic caching library has been introduced but needs to 
-   be applied to NK records at a minimum.  Eventually, VK records and 
-   data should also be cached separately and only be parsed when needed, 
-   rather than when a key is loaded up front.  Caching also needs 
-   configurable object limits, preferrably configurable at build-time.
-
- - It might be nice to have a way to filter results by security 
-   descriptor information.  Maybe by MTIME as well.
+ - Develop and solidify regfi API.  Regfi should be better documented and 
+   eventually needs a set of Python wrappers.
 
  - Documentation.  The security descriptor output format needs to be 
@@ -58 +55 @@
    dictate which version of conversion function is used.
 
- - It appears the registry may actually support UTF-16LE names on keys, 
-   if the key type field is set appropriately.  Once data parsing is 
-   integrated into regfi, then the UTF-16LE handling routines (which 
-   would then be built-in) should be used to properly handle this case.
-
  - Grep through the source for 'XXX', and you'll find more.