TL;DR: The Single Instance Store is described, a component within Windows® 2000 that implements links with the semantics of copies for files stored on a Windows 2000 NTFS volume, and other possible uses of SIS are discussed.
Abstract: Certain applications, such as Windows 2000's Remote Install service, can result in a set of files in which many different files have the same content. Using a traditional file system to store these files separately results in excessive use of disk and main memory file cache space. Using hard or symbolic links would eliminate the excess resource requirements, but changes the semantics of having separate files, in that updates to one "copy" of a file would be visible to users of another "copy." We describe the Single Instance Store (SIS), a component within Windows® 2000 that implements links with the semantics of copies for files stored on a Windows 2000 NTFS volume. SIS uses copy-on-close to implements the copy semantics of its links. SIS is structured as a file system filter driver that implements links and a user level service that detects duplicate files and reports them to the filter for conversion into links. Because SIS links are semantically identical to separate files, SIS creates them automatically when it detects files with duplicate contents. This paper describes the design and implementation of SIS in detail, briefly presents measurements of a remote install server showing a 58% disk space savings by using SIS, and discusses other possible uses of SIS.
TL;DR: In this article, the authors propose a method and apparatus for enforcing software licenses for resource libraries such as an application program interface (API), a toolkit, a framework, a runtime library, a dynamic link library (DLL), an applet (e.g., a Java or ActiveX applet), or any other reusable resource.
Abstract: A method and apparatus for enforcing software licenses for resource libraries such as an application program interface (API), a toolkit, a framework, a runtime library, a dynamic link library (DLL), an applet (e.g., a Java or ActiveX applet), or any other reusable resource. The resource library can be used by authorized end user software programs. A “per-program” licensing scheme for a resource library can allow a resource library to be licensed only for use with particular software programs.
TL;DR: In this paper, a multi-language user interface (MUI) for use in a mobile electronic device accesses language-dependent information (e.g., resource strings, settings stored in a registry, or file names).
Abstract: A multi-language user-interface (MUI) for use in a mobile electronic
device accesses language-dependent information. The MUI system includes a
display, an operating system, a localized data store, and an application. The MUI
system is used in displaying information in a selected language on the mobile
electronic device. The needed language-dependent information may be localized or
include a portion that is localized. When the application needs to display localized
language-dependent information ( e.g. , resource strings, settings stored in a registry,
or file names), this information is obtained from the localized data store, which also
contains language-dependent for all of the languages supported by the mobile
electronic device.
TL;DR: In this paper, a multi-language user interface (MUI) for use in a mobile electronic device accesses language-dependent information (e.g., resource strings, settings stored in a registry, or file names).
Abstract: A multi-language user-interface (MUI) for use in a mobile electronic device accesses language-dependent information. The MUI system includes a display, an operating system, a localized data store, and an application. The MUI system is used in displaying information in a selected language on the mobile electronic device. The needed language-dependent information may be localized or include a portion that is localized. When the application needs to display localized language-dependent information (e.g., resource strings, settings stored in a registry, or file names), this information is obtained from the localized data store, which also contains language-dependent for all of the languages supported by the mobile electronic device.