Portable cross platform database accessing method and system

• US 7,418,665 B2
• Filed: 10/16/2002
• Issued: 08/26/2008
• Est. Priority Date: 10/16/2002
• Status: Expired due to Fees

• Current Assignee: Mozapps Limited
• Original Assignee: Shaun Savage
• Inventors: Savage, Shaun
• Primary Examiner(s): Nguyen; Cao (Kevin)
• Application Number:
  US10/271,625
• Publication Number:
  US 20040075683A1
• Time in Patent Office: 2,141 Days
• Field of Search: 715763-765, 715/840, 715/853, 715/855, 715/854, 709/229, 709/210
• US Class Current: 715/763
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application

Abstract

A user manages a database or other application through a remote graphical user interface on a server device through a client device. A cross platform database translation module resides on the client device. The client device may also store cross platform authentication, configuration, and report generating modules for validating a user id and presenting database results in a desirable format. The modules on the client device request applications from a server device, may request validation from an authorization server, may configure embedded devices, and may query a database. The database may reside on a server, on the client device, or on another device.

Claims

1. A database accessing graphical user interface (GUI) system, comprising:

a user device having a resident database translation module which utilizes an ACL (access control list) to control access and a cache memory which cannot be accessed by direct memory access;

a server device having a resident XUL (Extensible User Interface Language) graphical user interface program, the server device dynamically providing at least a portion of an application upon request to the cache memory of the user device on a need to know basis to control access to the application, wherein access to the application in the cache memory is controlled because the cache memory cannot be accessed by direct memory access; and

a database accessed by the user device through native binary calls.

2. The database accessing GUI system of claim 1, wherein the resident database translation module includes a first module and a second module.

3. The database accessing GUI system of claim 2, wherein the first module is written in a binary code.

4. The database accessing GUI system of claim 3, wherein the binary code is C++.

5. The database accessing GUI system of claim 4, wherein the second module is a security module.

6. The database accessing GUI system of claim 1, wherein the resident database translation module is platform independent.

7. The database accessing GUI system of claim 1, wherein the user device is a handheld device.

8. The database accessing GUI system of claim 1, wherein the user device is a work station.

9. The database accessing GUI system of claim 1, wherein the database resides on the user device.

10. The database accessing GUI system of claim 1, wherein the database resides on the server device.

11. The database accessing GUI system of claim 1, further comprising another device upon which the database resides.

12. The database accessing GUI system of claim 1, further comprising an embedded device operatively coupled to the user device.

13. The database accessing GUI system of claim 12, wherein the user device requests configuration information from the embedded device.

14. The database accessing GUI system of claim 12, wherein the user device updates configuration information on the embedded device.

15. The database accessing GUI of claim 1, wherein the database is secured.

16. The database accessing GUI of claim 15, wherein the database is secured by an encrypted key.

17. A method for accessing a database through a remote graphical user interface, comprising the steps of:

displaying a XUL (Extensible User Interface Language) graphical user interface on a client device which includes a cache memory which cannot be accessed by direct memory access;

entering a request for authorization on the client device;

validating the authorization on a first external device, utilizing an ACL (access control list) to control access;

if the authorization is validated, then requesting an application by a user from the client device to a second external device;

receiving at least a portion of the requested application dynamically on the cache memory of the client device on a need to know basis to control access to the application, wherein access to the application in the cache memory is controlled because the cache memory cannot be accessed by direct memory access; and

querying a database external to the client device through native binary calls.

18. The method of claim 17, wherein the step of querying the database external to the client device is performed through the structured query language (SQL).

19. The method of claim 17, wherein the step of querying the database external to the client device is performed through a component object model module.

20. The method of claim 19, wherein the component object model module is a cross platform component object model module.

21. The method of claim 17, further comprising the step of receiving database results by the client device from the database.

22. The method of claim 21, wherein the step of querying the database and the step of receiving database results is accomplished through native database drivers.

23. The method of claim 17, wherein code for the graphical user interface resides on the first external device.

24. The method of claim 17, wherein the first external device is a cross platform authentication (XPAUTH) server.

25. The method of claim 17, wherein the second external device is an applications server.

26. The method of claim 17, wherein the step of validating the user includes providing fine grain access to the database or network service.

27. The method of claim 17, wherein the step of validating the user includes providing complete access to the database.

28. The method of claim 17, wherein the request for authorization is through a user id.

29. The method of claim 17, wherein the request for authorization is through a token.

30. The method of claim 29, wherein the token is a hardware token that passes within a certain distance of the client device to provide authorization.

31. The method of claim 29, wherein the token is a software token.

32. The method of claim 17, wherein the request for authorization is through a smart card.