Scalable computing system for managing dynamic communities in multiple tier computing system
First Claim
1. A multiple tier computer system for scalably managing dynamic communities, the multiple tier computing system comprising:
- a plurality of community elements;
a server for storing indices of the plurality of community elements at a first tier; and
one or more persistent data stores for storing the plurality of community elements at a second tier, wherein response to a request to access one or more of the community elements the server assembles the community elements and dynamically generates one or more pages; and
wherein complex queries of said community elements are reduced to improve scalability by querying said indices to access said community elements.
2 Assignments
0 Petitions
Accused Products
Abstract
A scalable computing system for managing dynamic communities stores and provides access to community and member information. A community is a dynamic and virtual association of users. Some example features of a community include: a home page, membership, non-real time based messaging (threaded messages), chats, community calendar, annotations, and management tools for access control. The scalable architecture of the computing system for managing dynamic communities provides a computing system capable of handling the increasing number of community members and the community elements associated with the community.
55 Citations
19 Claims
-
1. A multiple tier computer system for scalably managing dynamic communities, the multiple tier computing system comprising:
-
a plurality of community elements;
a server for storing indices of the plurality of community elements at a first tier; and
one or more persistent data stores for storing the plurality of community elements at a second tier, wherein response to a request to access one or more of the community elements the server assembles the community elements and dynamically generates one or more pages; and
wherein complex queries of said community elements are reduced to improve scalability by querying said indices to access said community elements. - View Dependent Claims (2, 3)
-
-
4. A scalable computerized method of managing dynamic communities, the method comprising:
-
storing a plurality of community elements within a multiple tier computing system;
receiving a request from a client to access one or more the community elements at a first tier;
assembling the community elements as a function of the request from a second tier;
dynamically generating one or more pages of the assembled elements for display by the client; and
wherein to improve scalability said one ore more pages are generated with a reduced number of complex queries for said community elements. - View Dependent Claims (5, 6, 7, 8)
-
-
9. A computing system for scalably managing dynamic communities and for managing annotations, the computing system comprising:
-
a tier III server to store data for the annotations;
a tier II server to maintain an index of the data for the annotations stored on the tier III server, to store community elements, and to process community queries; and
a tier I server to determine if a content source has annotations indexed by the tier II server an to indicate which communities own the annotations, thereby reducing number of complex queries for said annotations to improve scalability. - View Dependent Claims (10, 11, 12, 13, 14)
-
-
15. A computer readable medium having computer executable instructions for a scalable method of managing dynamic communities stored thereon, the method comprising:
-
storing a plurality of community elements in a multiple tier computing system;
receiving a request from a client to access one or more of the community elements from a first tier;
assembling the community elements as a function of the request from a second tier;
dynamically generating one or more pages of the assembled elements for display by the client; and
wherein to improve scalability said one or more pages are generated with a reduced number of complex queries for said community elements. - View Dependent Claims (16, 17, 18, 19)
-
Specification