Hosted application server

• US 8,346,950 B1
• Filed: 05/19/2005
• Issued: 01/01/2013
• Est. Priority Date: 05/19/2005
• Status: Expired due to Fees

• Current Assignee: Glam Media Incorporated (Glam Holdings Ltd.)
• Original Assignee: Glam Media Incorporated (Glam Holdings Ltd.)
• Inventors: Andreessen, Marc L., Vassallo, Steven, Gately, Dermot Martin, Meeks, Eric Reed
• Primary Examiner(s): Lin, Kenny
• Assistant Examiner(s): BEHARRY, NOEL R
• Application Number:
  US11/134,250
• Time in Patent Office: 2,784 Days
• Field of Search: 709/229, 715/234, 715/239, 719/311
• US Class Current: 709/229
• CPC Class Codes: G06F 9/468 Specific access rights for resources, e.g. using capability register

Abstract

A hosted application server system and method are disclosed. The hosted application server system includes an interface for receiving a request from one of a plurality of users, a runtime environment for running a plurality of independent applications, a core configured to receive and respond to a request from one of the applications, and an interface for sending a response to the user. The core can have access to a shared data model.

Claims

1. A hosted application server system, including:

a computer readable storage device comprising;

an interface for receiving a request from one of a plurality of users;

a runtime environment for running a plurality of independently authored applications, at least two of the applications being written in different programming languages;

a shared data model;

a core configured to receive and respond to a request from one of the independently authored applications for a content object from the shared data model; and

an interface for sending a response to the user;

wherein the shared data model is accessed and modified by more than one of the plurality of independently authored applications and stores data comprising;

a plurality of object types, an object type having a plurality of attributes that define data structure of a content object to which the object type corresponds, wherein one or more object types are user defined, and

a plurality of user-contributed content objects, wherein;

each user-contributed content object is associated with at least one of the object types, has data structured according to that object type, and is designated as being either publicly available to users other than a user who contributed the object or privately available only to the user who contributed the object,

at least one of the user-contributed content objects is accessed by different ones of the plurality of independently authored applications, and

at least one of the user-contributed content objects has a user attribute identifying the user who contributed the content object to the shared data model.

2. The system of claim 1, wherein the applications are run at various levels of trust.

3. The system of claim 1, wherein the core is further configured to authenticate the user.

4. The system of claim 1, wherein the core is further configured to enforce security of the application based on the user or the application.

5. The system of claim 1, wherein the core is further configured to enforce security of the application based on a role associated with the user.

6. The system of claim 1, wherein the core is further configured to enforce security of content based on the user.

7. The system of claim 1, wherein the shared data model includes content associated with at least one user.

8. The system of claim 1, wherein at least one content object is associated with a view file that describes how the content object should be displayed, and the core is further configured to display the content object based at least in part on the associated view file.

9. The system of claim 1, wherein the shared data model comprises at least one content object associated with tags specified by a plurality of users.

10. The system of claim 1, wherein the users are handled at various levels of trust.

11. The system of claim 1, wherein the core is further configured to associate an identifier with the request.

12. The system of claim 1, wherein the core is further configured to associate an identifier with the request, wherein the identifier is associated with a role, a username, or an application.

13. The system of claim 1, wherein the core is further configured to associate an identifier with the request, wherein the identifier is a security token.

14. The system of claim 1, wherein the response sent to the user includes data from a shared data model.

15. The system of claim 1, wherein the response sent to the user includes advertising data.

16. The system of claim 1, wherein the response to the request from one of the applications includes data from the shared data model.

17. The system of claim 1, wherein the response from the application includes XML or HTML code.

18. The system of claim 1, wherein the response sent to the user includes HTML code.

19. The system of claim 1, wherein the core is further configured to provide system services.

20. The system of claim 1, wherein the server system is configured to run on the Internet.

21. The system of claim 1, wherein the plurality of independently authored applications are web-based applications.

22. The system of claim 1, wherein at least one of the user contributed objects has an object type defined by a user different from a user who contributed the object.

23. The system of claim 1, wherein the hosted application server has a plurality of language processors adapted to run the plurality of independently authored applications.

24. The system of claim 23, wherein the at least two applications written in different languages are written in procedural programming languages and generate HTML.

25. The system of claim 1, wherein at least one of the object types is accessed by different ones of the plurality of independently authored applications.

26. The system of claim 1, wherein the designation of public or private availability of a user-contributed content object is specified by the user who contributed the object.

27. The system of claim 1, wherein the user who contributed the object has an associated list of friends, and wherein each user-contributed content object is designated as being publicly available to users other than a user who contributed the object, or privately available only to the user who contributed the object or to a friend in the associated list of friends.

28. A method of delivering a page to a user, including:

receiving a request from one of a plurality of users;

receiving and responding to a request from one of a plurality of independently authored applications for a content object from a shared data model, at least two of the applications being written in different programming languages;

accessing the shared data model; and

sending a response to the user;

wherein the shared data model can be accessed and modified by more than one of the plurality of independently authored applications, and stores data comprising;

a plurality of object types, an object type having a plurality of attributes defining a data structure of a content object to which the object type corresponds, wherein one or more object types are user defined, and

a plurality of user-contributed content objects, wherein;

each user-contributed content object is associated with at least one of the object types, has data structured according to that object type, and is designated as being either publicly available to users other than a user who contributed the object or privately available only to the user who contributed the object,

at least one of the user-contributed content objects is accessed by different ones of the plurality of independently authored applications, and

at least one of the user-contributed content objects has a user attribute identifying the user who contributed the content object to the shared data model.

29. A computer program product for delivering a page to a user, the computer program product being persistently embodied in a computer readable storage medium and comprising computer instructions for:

receiving a request from one of a plurality of users;

receiving and responding to a request from one of a plurality of independently authored applications for a content object from a shared data model, at least two of the applications being written in different programming languages;

accessing the shared data model; and

sending a response to the user;

wherein the shared data model can be accessed and modified by more than one of the plurality of independently authored applications, and stores data comprising;

a plurality of object types, an object type having a plurality of attributes defining data structure of a content object to which the object type corresponds, wherein one or more object types are user defined, and

a plurality of user-contributed content objects, wherein;

each user-contributed content object is associated with at least one of the object types, has data structured according to that object type, and is designated as being either publicly available to users other than a user who contributed the object or privately available only to the user who contributed the object,

at least one of the user-contributed content objects is accessed by different ones of the plurality of independently authored applications, and

at least one of the user-contributed content objects has a user attribute identifying the user who contributed the content object to the shared data model.

30. A method of delivering a page to a user, including:

receiving a request from a user for a content object of a shared data model;

preprocessing the request within a server running a plurality of independently authored applications, at least two of the applications being written in different programming languages;

transmitting the preprocessed user request to an application;

receiving a response from the application, the response including the content object;

postprocessing the response; and

transmitting the postprocessed response to the user;

wherein the shared data model can be accessed and modified by more than one of the plurality of independently authored applications, and stores data comprising;

a plurality of object types, an object type having a plurality of attributes defining data structure of a content object to which the object type corresponds, wherein one or more object types are user defined, and

a plurality of user-contributed content objects, wherein;

each user-contributed content object is associated with at least one of the object types, has data structured according to that object type, and is designated as being either publicly available to users other than a user who contributed the object or privately available only to the user who contributed the object,

at least one of the user-contributed content objects is accessed by different ones of the plurality of independently authored applications, and

at least one of the user-contributed content objects has a user attribute identifying the user who contributed the content object to the shared data model.

31. The method of claim 30, further including receiving and responding to a request from the application.

32. The method of claim 30, wherein the applications are run at various levels of trust.

33. The method of claim 30, wherein preprocessing the request from the user includes authenticating the user.

34. A hosted application server system, including:

a computer readable storage device comprising;

an interface for receiving a request from one of a plurality of users for a content object of a shared data model;

a runtime environment for running a plurality of independently authored applications, at least two of the applications being written in different programming languages;

a core configured to;

preprocess the request from the user;

receive and respond to a request from one of the applications, the response including the content object; and

postprocess a response from the application; and

an interface for sending the postprocessed response to the user;

wherein the shared data model can be accessed and modified by more than one of the plurality of independently authored applications, and stores data comprising;

a plurality of object types, an object type having a plurality of attributes defining data structure of a content object to which the object type corresponds, wherein one or more object types are user defined, and

a plurality of user-contributed content objects, wherein;

each user-contributed content object is associated with at least one of the object types, has data structured according to that object type, and is designated as being either publicly available to users other than a user who contributed the object or privately available only to the user who contributed the object,

at least one of the user-contributed content objects is accessed by different ones of the plurality of independently authored applications, and

at least one of the user-contributed content objects has a user attribute identifying the user who contributed the content object to the shared data model.

35. A computer program product for delivering a page to a user, the computer program product being persistently embodied in a computer readable storage medium and comprising computer instructions for:

receiving a request from a user for a content object of a shared data model;

preprocessing the request within a server running a plurality of independently authored applications, at least two of the applications being written in different programming languages;

transmitting the preprocessed user request to an application;

receiving a response from the application, the response including the content object;

postprocessing the response; and

transmitting the post processed response to the user;

wherein the shared data model can be accessed and modified by more than one of the plurality of independently authored applications and stores data comprising;

a plurality of object types, an object type having a plurality of attributes defining data structure of a content object to which the object type corresponds, wherein one or more object types are user defined, and

a plurality of user-contributed content objects, wherein;

each user-contributed content object is associated with at least one of the object types, has data structured according to that object type, and is designated as being either publicly available to users other than a user who contributed the object or privately available only to the user who contributed the object,

at least one of the user-contributed content objects is accessed by different ones of the plurality of independently authored applications, and

at least one of the user-contributed content objects has a user attribute identifying the user who contributed the content object to the shared data model.