Sharing data in scalable software blade architecture
First Claim
1. A system comprising:
- a first blade server and a second blade server,wherein the first blade server and the second blade server each serves a predefined group of users,wherein the first blade server connects a first user to a first connected dataset and the second blade server connects a second user to a second connected dataset, the first user and the second user are each associated with one or more user devices,wherein the first blade server and the second blade server operate independently of each other,wherein each of the connected datasets is implemented by an aggregated backend including data available on backends of a plurality of associated content nodes, andwherein each of the connected datasets is accessible to the corresponding user via a plurality of user devices of the user;
a blade manager for managing the first and second blade servers;
a pipe device for connecting the first and second blade servers; and
wherein the at least one of the first blade server and the second blade server are configured for;
sharing portions of the first connected dataset of the first user with the second user using the pipe deviceidentifying a shared dataset and its corresponding access restrictions from the first connected dataset, the shared dataset comprising at least a portion of ˜
the first connected dataset;
transferring a copy of the shared dataset and its corresponding access restrictions from the first blade server to the second blade server, such that the Copy of the shared dataset is stored in the second connected dataset, and the copy of the access restrictions is stored on second blade server;
receiving modifications of the copy of the shared dataset stored in the second connected dataset by the second user at the second blade server according to the second user'"'"'s access restrictions stored on the copy of the access restrictions; and
propagating the modifications to the copy of the shared dataset stored in the second connected dataset from the second blade server to the first blade server using the pipe device such that the modifications are applied by the first blade server to the shared dataset in the first connected dataset.
9 Assignments
0 Petitions
Accused Products
Abstract
A system and method for sharing data between two users on different blades in scalable software blade architecture are disclosed. The system includes a plurality of blades, where each blade includes software components and hardware components, each blade serves a predefined group of users, and each user is associated with one or more user devices. The system further includes a first blade and a second blade, where the first blade connects a first user to a first connected dataset and the second blade connects a second user to a second connected dataset, and the first blade and the second blade operate independent of each other, a blade manager for managing the first and second blades, a pipe device for connecting the first and second blades, and logic for sharing portions of the first connected dataset of the first user with the second user using the pipe device.
105 Citations
24 Claims
-
1. A system comprising:
-
a first blade server and a second blade server, wherein the first blade server and the second blade server each serves a predefined group of users, wherein the first blade server connects a first user to a first connected dataset and the second blade server connects a second user to a second connected dataset, the first user and the second user are each associated with one or more user devices, wherein the first blade server and the second blade server operate independently of each other, wherein each of the connected datasets is implemented by an aggregated backend including data available on backends of a plurality of associated content nodes, and wherein each of the connected datasets is accessible to the corresponding user via a plurality of user devices of the user; a blade manager for managing the first and second blade servers; a pipe device for connecting the first and second blade servers; and wherein the at least one of the first blade server and the second blade server are configured for; sharing portions of the first connected dataset of the first user with the second user using the pipe device identifying a shared dataset and its corresponding access restrictions from the first connected dataset, the shared dataset comprising at least a portion of ˜
the first connected dataset;transferring a copy of the shared dataset and its corresponding access restrictions from the first blade server to the second blade server, such that the Copy of the shared dataset is stored in the second connected dataset, and the copy of the access restrictions is stored on second blade server; receiving modifications of the copy of the shared dataset stored in the second connected dataset by the second user at the second blade server according to the second user'"'"'s access restrictions stored on the copy of the access restrictions; and propagating the modifications to the copy of the shared dataset stored in the second connected dataset from the second blade server to the first blade server using the pipe device such that the modifications are applied by the first blade server to the shared dataset in the first connected dataset. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method comprising:
-
providing a first blade server and a second blade server, wherein the first blade server and the second blade server each serves a predefined group of users, wherein the first blade server connects a first user to a first connected dataset and the second blade server connects a second user to a second connected dataset, the first user and the second user each associated with one or more user devices, wherein the first blade server and the second blade server operate independent of each other, wherein each of the connected datasets is implemented by an aggregated backend including data available on backends of a plurality of associated content nodes, and wherein each of the connected datasets is accessible to the corresponding user via a plurality of user devices of the user; managing the first and second blade servers by a blade manager; providing a pipe device for connecting the first and second blade servers; and sharing portions of the first connected dataset of the first user with the second user using the pipe device; identifying a shared dataset and its corresponding access restrictions from the first connected dataset, the shared dataset comprising at least a portion of the first connected dataset; transferring a copy of the shared dataset and its corresponding access restrictions from the first blade server to the second blade server, such that the copy of the shared dataset is stored in the second connected dataset, and the copy of the access restrictions is stored on the second blade server; receiving modifications of the copy of the shared dataset stored in the second connected dataset by the second user at the second blade server according to the second user'"'"'s access restrictions stored on the copy of the access restrictions; and propagating the modifications to the copy of the shared dataset stored in the second connected dataset from the second blade server to the first blade server using the pipe device such that the modifications are applied by the first blade server to the shared dataset in the first connected dataset. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
-
-
17. A computer readable storage medium for tangibly storing thereon computer readable instructions comprising:
-
code for operating a first blade server and a second blade server, wherein the first blade server and the second blade server each serves a predefined group of users, wherein the first blade server connects a first user to a first connected dataset and the second blade server connects a second user to a second connected dataset, the first user and the second user associated with one or more user devices, wherein the first blade server and the second blade server operate independent of each other, wherein each of the connected datasets is implemented by an aggregated backend including data available on backends of a plurality of associated content nodes, and wherein each of the connected datasets is accessible to the corresponding user via a plurality of user devices of the user; code for managing the first and second blade servers by a blade manager; code for connecting the first and second blade servers by a pipe device; and code for sharing portions of the first connected dataset of the first user with the second user using the pipe device; code for identifying a shared dataset and its corresponding access restrictions from the first connected dataset, the shared dataset comprising at least a portion of the first connected dataset; code for transferring a copy of the shared dataset and its corresponding access restrictions from the first blade server to the second blade server, such that the copy of the shared dataset is stored in the second connected dataset, and the copy of the access restrictions are stored on the second blade server; code for receiving modifications of the copy of the shared dataset stored in the second connected dataset by the second user at the second blade server according to the second user'"'"'s access restrictions stored on the copy of the access restrictions; and code for propagating the modifications to the copy of the shared dataset stored in the second connected dataset from the second blade server to the first blade server using the pipe device such that the modifications are applied by the first blade server to the shared dataset in the first connected dataset. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24)
-
Specification