Computing system and method to implicitly commit unsaved data for a world wide Web application

• US 20050131925A1
• Filed: 01/06/2005
• Published: 06/16/2005
• Est. Priority Date: 09/29/2001
• Status: Active Grant

• Current Assignee: Anil Mukundan, John Coker
• Original Assignee: Anil Mukundan, John Coker
• Inventors: Mukundan, Anil, Coker, John
• Granted Patent: US 7,953,760 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

In one embodiment, the invention is a computing system comprising a World Wide Web application with a user interactive record field is described. The record field receives a record field entry. The application receives a context change request. Responsive to the context change request, the application dynamically transmits the record field entry to a server for storage in a database.

Claims

1-21. -21. (canceled)

22. A method, comprising:

receiving an entry in a user interactive record field;

receiving a context change request; and

in response to the context change request and determining the entry has not been transmitted to a web server for storage, transmitting the entry to the web server.

23. The method of claim 22, wherein the context change request is a World Wide Web browser view change.

24. The method of claim 22, wherein the context change request is an active applet change.

25. The method of claim 22, wherein the context change request is a change in a record field selected for editing.

26. The method of claim 22, further comprising storing the entry by using a client cache.

27. The method of claim 26, further comprising maintaining the entry in the cache until the entry is transmitted to the server.

28. The method of claim 22, further comprising an application in a web client controlling all direct communications with the server.

29. A computer-readable medium having stored thereon a set of instructions, which when executed perform a method comprising:

receiving an entry in a user interactive record field;

receiving a context change request; and

in response to the context change request and determining the entry has not been transmitted to a web server for storage, transmitting the entry to the web server.

30. The medium of claim 29, wherein the context change request is one of:

a view change;

an active applet change; and

a change in a record field selected for editing.

31. The medium of claim 29, further comprising storing the entry by using a client cache.

32. The medium of claim 31, further comprising:

maintaining the entry in the cache until the entry is transmitted to the server; and

responsive to said transmitting, clearing the cache.

33. A data processing system, comprising:

means for receiving an entry in a user interactive record field;

means for receiving a context change request; and

means for, in response to the context change request and determining the entry has not been transmitted to a web server for storage, transmitting the entry to the web server.

34. The data processing system of claim 33, further comprising:

means for receiving a notification from the server; and

means for transmitting the context change request to the server responsive to the notification indicating that the entry is committed into a database.

35. The data processing system of claim 34, wherein transmission of the context change request to the server is held off when the notification indicates an error in committing the entry into the database.

36. The data processing system of claim 33, wherein the entry is transmitted to the server without the context change request being transmitted to the server.

37. The data processing system of claim 36, further comprising:

means for determining whether or not the entry is already saved into the database;

wherein in response to the request and a determination that the entry is already saved into the database, the entry is not transmitted to the server.

38. The data processing system of claim 33, wherein the entry is maintained in a cache before the entry is transmitted to the server;

and the entry is not maintained in the cache after the entry is transmitted to the server.

39. The data processing system of claim 33, wherein the request is responsive to a user request to tab out of the record field.

40. The data processing system of claim 39, wherein the entry is transmitted from to the server using a remote procedure call (RPC) module.

41. The data processing system of claim 33, wherein the request does not unconditionally require transmission of record field data to the server.