Method and system for distributing objects over a network

• US 6,604,128 B2
• Filed: 10/23/2001
• Issued: 08/05/2003
• Est. Priority Date: 11/30/1999
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Diec, Thanh
• Primary Examiner(s): Jean, Frantz B.
• Application Number:
  US09/983,064
• Publication Number:
  US 20020042843A1
• Time in Patent Office: 651 Days
• Field of Search: 709/203, 709/227, 709/230, 709/200, 709/217, 709/219, 709/218, 709/228
• US Class Current: 709/203
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 16/986 Document structures and storage, e.g. HTML extensions
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

A method and system for passing information between a client, as a browser, and a server, as an application server, where the information is passed through a web server for processing between the application server and the browser. The webserver loads one or more template files. These template files contain standard markup language plus special tags. These tags are parsed, translated into commands for the application server, and sent to the application server. The application server returns the objects called to the web server, which passes the called objects to the client. The session is persistent.

Claims

1. Computer executable software code for passing information between a client browser and an application server, said software code comprising:

code to send a markup language form including encoded metadata information to the client browser;

code to receive information in response to the encoded metadata information;

code to load one or more template files including embedded tags based upon the information received from the client;

code to retrieve one or more objects stored on the application server, wherein the one or more objects are called by the embedded tags;

code to convert the one or more objects into markup language; and

code to transmit the markup language to the client browser.

2. The software code of claim 1, wherein information is exchanged with the client browser via a persistent connection.

3. The software code of claim 2, wherein the objects are selected from the group consisting of views, applets, fields, data, and links.

4. The software code of claim 1, wherein at least a portion of the software code is resident on a web server.

5. The software code of claim 1, wherein the embedded tags have the format <

TagCall TagNameCall=“

TagName”

/>

where TagCall indicates that the command inside the braces is a tag call, TagNameCall indicates the name of the object being called, TagName is the name of the tag being called, and “

/”

ends the tag.

6. The software code of claim 1, wherein the one or more objects are selected from the group consisting of function objects, data objects, and application objects.

7. The software code of claim 1, wherein the objects are selected from the group consisting of views, applets, fields, data, and links.

8. A web server for passing information between a client browser and an application server comprising:

means for sending a markup language form including encoded metadata information to the client browser;

means for receiving information in response to the encoded metadata information;

means for loading one or more template files including embedded tags based upon the information received from the client;

means for retrieving one or more objects stored on the application server, wherein the one or more objects are called by the embedded tags;

means for converting the one or more objects into markup language; and

means for transmitting the markup language to the client browser.

9. The web server of claim 8, wherein a persistent connection is established between the web server and the client browser.

10. The web server of claim 9, wherein the objects are selected from the group consisting of views, applets, fields, data, and links.

11. The web server of claim 8, wherein the embedded tags have the format <

TagCall TagNameCall=“

TagName”

/>

where TagCall indicates that the command inside the braces is a tag call, TagNameCall indicates the name of the object being called, TagName is the name of the tag being called, and “

/”

ends the tag.

12. The web server of claim 8, wherein the one or more objects are selected from the group consisting of function objects, data objects, and application objects.

13. The web server of claim 8, wherein the objects are selected from the group consisting of views, applets, fields, data, and links.

14. A method for passing information between a client browser and an application server comprising:

sending a markup language form including encoded metadata information to the client browser;

receiving information in response to the encoded metadata information;

loading one or more template files including embedded tags based upon the information received from the client;

retrieving one or more objects stored on the application server, wherein the one or more objects are called by the embedded tags;

converting the one or more objects into markup language; and

transmitting the markup language to the client browser.

15. The method of claim 14, further comprising establishing a persistent connection with the client browser.

16. The method of claim 15, wherein the objects are selected from the group consisting of views, applets, fields, data, and links.

17. The method of claim 14, wherein the embedded tags have the format <

TagCall TagNameCall=“

TagName”

/>

where TagCall indicates that the command inside the braces is a tag call, TagNameCall indicates the name of the object being called, TagName is the name of the tag being called, and “

/”

ends the tag.

18. The method of claim 14, wherein the one or more objects are selected from the group consisting of function objects, data objects, and application objects.

19. The method of claim 14, wherein the objects are selected from the group consisting of views, applets, fields, data, and links.