ONLINE LIBRARY FEATURING RELIGIOUS

Brand	Owner (click to sort)	Address	Description
DBL	UNITED BIBLE SOCIETIES ASSOCIATION, INC.	11401 S.W. 40 Street, Ste. 201 Miami FL 33165	an online library featuring religious works;
DBL	UNITED BIBLE SOCIETIES ASSOCIATION, INC.	11401 S.W. 40 Street, Ste. 201 Miami FL 33165	an online library featuring religious works;The mark consists of a black rectangular field with rounded corners within which the term DBL appears in white, lower case typeface above two curved ribbons and below a series of binary numbers which appear to the left of four small squares.;DIGITAL BIBLE LIBRARY;Color is not claimed as a feature of the mark.;
DBL THE DIGITAL BIBLE LIBRARY	UNITED BIBLE SOCIETIES ASSOCIATION, INC.	11401 S.W. 40 Street, Ste. 201 Miami FL 33165	an online library featuring religious works;The mark consists of a black rectangular field with rounded corners within which the term DBL appears in white, lower case typeface above two curved ribbons and below a series of binary numbers which appear to the left of four small squares. The wording THE DIGITAL BIBLE LIBRARY appearing to the right hand side of the rectangular field.;Color is not claimed as a feature of the mark.;DIGITAL BIBLE LIBRARY;
	Where the owner name is not linked, that owner no longer owns the brand

Technical Examples

A method and system for providing "just-in-time" dynamic loading and unloading of libraries. Library code is loaded into memory just prior to the actual execution of a routine in that library and is unloaded from memory after the execution of the library routine is completed. According to the present invention, a library structure having a library loader and a library implementation module. The library loader provides the same entry points as the library itself and contains code to drive the loading and unloading of the library implementation module which actually contains the code to implement the library call. At the beginning of the execution of an application or other software module, the library loaders for libraries needed by that application or other software module, are loaded into memory and unloaded upon completion of that application or other software module. The library loaders control the loading and unloading of the library implementation modules, which contain the actual code which implements the library call, so that the library code itself is only in memory while in use during execution of the library call. A sequence of library calls to the same library is preferably detected and managed so as to avoid unnecessary unloading/reloading of the same library.