Loading patent…
AssigneeNone recorded
InventorMayel Espino
Estimating the term…
A device and computer-readable medium, including an application for communicating with a directory server. The application submits a query to the directory server requesting data for the application. In response to a query result that includes the requested data from the directory server, the application stores the received data for display on the device. In another aspect, there is provided a device, including a client process for running on the device and for communicating with a directory server; and an application for running on the device. The client process submits a query to the directory server requesting data for the application. In response to a query result that includes the requested data from the directory server, the client process stores the received data for display on the device by the application.
A device, comprising:
A computer-readable medium, comprising:
A device, comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
Backward citations are indexed for grants only.
Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection: user interfaces…
Browsing optimisation, e.g. caching or content distillation: optimising the visualization of content, e.g. distillation of HTML documents
Providing data content: by data transmission, e.g. downloading
With means for local support of applications that increase the functionality: for supporting Internet browser applications
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, system and computer program product for lightweight directory access protocol applications.
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 lightweight directory access protocol (LDAP) applications, 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/HTTP-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, Mar. 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, 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.