diff --git a/xpcom/doc/xpcom-component-registration.html b/xpcom/doc/xpcom-component-registration.html index c97fe1feae86..c029bd5ab37e 100644 --- a/xpcom/doc/xpcom-component-registration.html +++ b/xpcom/doc/xpcom-component-registration.html @@ -47,19 +47,23 @@ pairs associated with each key. Each key also keeps a default value.
        CLSID
            "CLSID-string"    "class name" -
               +
              + ProgID        "component.class.version" -
               +
              + InprocServer  "full-path-name"
                    LastModTimeStamp*   time-value -
                   -FileSize*          +
                  + +FileSize*         + nbytes -
    "component.class.version"    +
        "component.class.version"    "class name" -
        CLSID        -"CLSID-string" +
            +CLSID        "CLSID-string"


* Automatically added by the Repository @@ -192,11 +196,11 @@ Need support for questions like: Enumerate all CLSIDs that implement a particular interface.

  • -Let a particular CLSID be the preferable implementation for an interface.
    -I dont know how this a XPCOM component user could use it unless there could -be a call like:
    -nsIRepository::CreateInstance(NULL, NULL, nsWidgetIID, &result);
  • +Let a particular CLSID be the preferable implementation for an interface. +
    I dont know how this a XPCOM component user could use it unless there +could be a call like: +
    nsIRepository::CreateInstance(NULL, NULL, nsWidgetIID, &result);
  • Enumerate all interfaces supported by a CLSID
  • @@ -208,8 +212,8 @@ Resolving naming conflicts between ProgID Store component specific name-values under ROOTKEY_COMMON\\component.class.version\\
  • -Add a registry entry under ROOTKEY_COMMON\\component.class.version\\ -to indicate the willingness for a CLSID to behave as a Service.
  • +Add a registry entry under ROOTKEY_COMMON\\component.class.version\\to +indicate the willingness for a CLSID to behave as a Service.
  • Add quick registration support functions in nsIRepository for