Loading patent…
AssigneeNone recorded
InventorMayel Espino
Estimating the term…
A client architecture, including, on a device, a plurality of processes executing on the device; and a client for receiving requests from the plurality of processes and for generating a query in accordance with a directory service protocol based on the received requests. In another aspect there is provided a client architecture, including, on a computer readable medium, a plurality of applications for executing on a device; and a client for receiving requests from a plurality of processes corresponding to the plurality of applications and for generating a query in accordance with a directory service protocol based on the received requests.
A client architecture, comprising, on a device:
A client architecture, comprising, on a computer readable medium:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
No related US applications are recorded in the indexed filing history.
Backward citations are indexed for grants only.
Using standardised directories; using standardised directory access protocols: using lightweight directory access protocol [LDAP]
Protocols: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
Digital communication
Term end not estimated
1. Field of the Invention
The present invention relates to the lightweight directory access protocol and more particularly to a method, device and computer program product for a lightweight directory access protocol client architecture.
2. Discussion of the Background
The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
FIG. 1 is a block diagram illustrating a lightweight directory access protocol (LDAP) system;
FIG. 2 is a block diagram illustrating a logical architecture of a LDAP device of the system of FIG. 1;
A method, device and computer program product for a lightweight directory access protocol (LDAP) client architecture, are described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It is apparent to one skilled in the art, however, that the present invention may be practiced without these specific details or with an equivalent arrangement. In some instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.
The present invention includes numerous advantages over conventional HTML-based systems and methods typically used in hand-held devices. In this respect, the present invention includes recognition that HTML/HTTP may be bloated when compared to lightweight directory access protocol (LDAP, e.g., as taught in “Implementing LDAP,” by Mark Wilcox, March 1999, the entire contents of which are incorporated herein by reference). Accordingly, a HTML/HTTP Web browser function typically needs more instructions to render an HTML document than a thin LDAP client according to the present invention uses to process and reply to a query and perform a similar function.
In addition, a Web browser function using HTML/HTTP would typically need cache to store the HTML and perhaps images, whereas a thin LDAP client according to the present invention typically employs only the space needed to store query results and the space to store the query results may be configured. Further, for the types of services and applications that the present invention suggests (e.g., as described in commonly owned co-pending U.S. patent application filed herewith, entitled “METHOD, SYSTEM AND COMPUTER PROGRAM PRODUCT FOR LIGHTWEIGHT DIRECTORY ACCESS PROTOCOL APPLICATIONS,” Ser. No. ______, ATTY. DOCK. NO. 09710-1091/COS-01-020), there may be typically no need for intensive graphics or an exuberant layout. Moreover, LDAP results in less network traffic than HTML/HTTP because in HTML/HTTP each request constitutes a new session or connection, whereas with LDAP functions that would employ multiple HTML/HTTP requests may be accomplished via a single LDAP query.