Abstract: The present teaching relates to a method, system, and programming for determining a source of a data object. A first average latency of a plurality of users in accessing the data object from the first data source is computed, wherein the first data source was previously identified as being the source of the data object. From each of other data sources, a second average latency of the plurality of users in accessing the data object from the other data source is obtained. In response to the first data source satisfying a first criterion associated with the first average latency, the first data source is maintained to be the source of the data object. In response to the first data source violating the first criterion, one of the other data sources that satisfies a second criterion associated with the second average latency is deemed as the source of the data object.

Abstract: The present teaching relates to a method, system, and programming for determining a source of a data object. A first average latency of a plurality of users in accessing the data object from the first data source is computed, wherein the first data source was previously identified as being the source of the data object. From each of other data sources, a second average latency of the plurality of users in accessing the data object from the other data source is obtained. In response to the first data source satisfying a first criterion associated with the first average latency, the first data source is maintained to be the source of the data object. In response to the first data source violating the first criterion, one of the other data sources that satisfies a second criterion associated with the second average latency is deemed as the source of the data object.

Abstract: The present teaching relates to continuing a user session of an application from one device to another device. Information related to a first session of a first application installed on a first device is received subsequent to the first device being instructed to collect the information. The first session information may indicate content and content presentation provided via the first application. The information related to the first session is provided to a second device so that a second session of a second application at the second device provides the same content in the same presentation as in the first session. The first and second sessions both may be associated with a same specific user identity, and the first and second applications have at least one common function.

Abstract: Images are optimized to reduce latency prior to being transmitted to requesting client devices. A request from a client device for an image is analyzed to obtain the attributes of the requesting client device and the network used by the client device for transmitting the request. The parameters of the image to be transmitted are determined based on the attributes in order to reduce data latency at the requesting client device. A requested image that meets the parameters or which has its parameters preset by a provider can be transmitted without any changes. A requested image that does not meet the parameters is transformed in accordance with the parameters so that it is optimized for the combination of the network and the requesting client device.

Abstract: Images are optimized to reduce latency prior to being transmitted to requesting client devices. A request from a client device for an image is analyzed to obtain the attributes of the requesting client device and the network used by the client device for transmitting the request. The parameters of the image to be transmitted are determined based on the attributes in order to reduce data latency at the requesting client device. A requested image that meets the parameters or which has its parameters preset by a provider can be transmitted without any changes. A requested image that does not meet the parameters is transformed in accordance with the parameters so that it is optimized for the combination of the network and the requesting client device.

Abstract: The present teaching relates to creating and updating a user profile related to multiple devices, and synchronizing applications' sessions for the user on different devices. Upon execution of a first application on a first device, a first device ID associated with the first device and information about the first application are received. A user profile is created based on the first device ID and the information about the first application. Upon execution of a second application on a second device related to the first device, a second device ID associated with the second device and information about the second application are received. The user profile is updated based on the second device ID and the information about the second application. Further, the information about the first application is applied to the execution of the second application on the second device, or vice-versa.

Abstract: The present teaching relates to continuing a user session of an application from one device to another device. Information related to a first session of a first application installed on a first device is received subsequent to the first device being instructed to collect the information. The first session information may indicate content and content presentation provided via the first application. The information related to the first session is provided to a second device so that a second session of a second application at the second device provides the same content in the same presentation as in the first session. The first and second sessions both may be associated with a same specific user identity, and the first and second applications have at least one common function.

Abstract: The present teaching relates to creating and updating a user profile related to multiple devices, and synchronizing applications' sessions for the user on different devices. Upon execution of a first application on a first device, a first device ID associated with the first device and information about the first application are received. A user profile is created based on the first device ID and the information about the first application. Upon execution of a second application on a second device related to the first device, a second device ID associated with the second device and information about the second application are received. The user profile is updated based on the second device ID and the information about the second application. Further, the information about the first application is applied to the execution of the second application on the second device, or vice-versa.

Abstract: The present teaching relates to continuing a user session of an application from one device to another device. Information related to a first user session of a first application installed on a first device is received. The first user session information may indicate content and content presentation provided via the first application. A request, based on a pre-defined URL, for the first session information is received from a second device. Responsive to the request, the information related to the first user session is provided to the second device so that a second user session of a second application at the second device provides the same content in the same presentation as in the first user session. The first and second user sessions both may be associated with a same specific user identity, and the first and second applications have at least one common function.

Abstract: Disclosed herein is a data synchronization between a client computing device's local store and another data store, such as a data store that is remote to the client computing device. The other data store may comprise a cloud data store. The existence, or absence, of a causal relationship between the local and remote data stores for a given data item is used to determine whether or not a conflict exists and/or whether a requested operation may be performed. The casual relationship may be determined using a previous commit's hash value, referred to as a hash_base value, and a hash value, both of which are associated with the data item.

Abstract: Disclosed herein is a data synchronization between a client computing device's local store and another data store, such as a data store that is remote to the client computing device. The other data store may comprise a cloud data store. The existence, or absence, of a causal relationship between the local and remote data stores for a given data item is used to determine whether or not a conflict exists and/or whether a requested operation may be performed. The causal relationship may be determined using a previous commit's hash value, referred to as a hash_base value, and a hash value, both of which are associated with the data item.

Abstract: Disclosed herein is a data synchronization between a client computing device's local store and another data store, such as a data store that is remote to the client computing device. The other data store may comprise a cloud data store. The existence, or absence, of a causal relationship between the local and remote data stores for a given data item is used to determine whether or not a conflict exists and/or whether a requested operation may be performed. The causal relationship may be determined using a previous commit's hash value, referred to as a hash_base value, and a hash value, both of which are associated with the data item.

Abstract: Automated centralized access to and management of content items stored on a plurality of content sources is provided. A content services module receives information regarding content sources which comprise third-party cloud storage servers and a user's personal computing devices in addition to receiving the user's access tokens for secured content sources. The content services modules act as a proxy for the user to the content sources and enables the user to execute various tasks across the content items stored in the various content sources via the interface.

Abstract: The present teaching relates to creating and updating a user profile related to multiple devices, and synchronizing applications' sessions for the user on different devices. Upon execution of a first application on a first device, a first device ID associated with the first device and information about the first application are received. A user profile is created based on the first device ID and the information about the first application. Upon execution of a second application on a second device related to the first device, a second device ID associated with the second device and information about the second application are received. The user profile is updated based on the second device ID and the information about the second application. Further, the information about the first application is applied to the execution of the second application on the second device, or vice-versa.

Abstract: The present teaching relates to continuing a user session of an application from one device to another device. Information related to a first user session of a first application installed on a first device is received. The first user session information may indicate content and content presentation provided via the first application. A request, based on a pre-defined URL, for the first session information is received from a second device. Responsive to the request, the information related to the first user session is provided to the second device so that a second user session of a second application at the second device provides the same content in the same presentation as in the first user session. The first and second user sessions both may be associated with a same specific user identity, and the first and second applications have at least one common function.

Abstract: Disclosed herein is a data synchronization between a client computing device's local store and another data store, such as a data store that is remote to the client computing device. The other data store may comprise a cloud data store. The existence, or absence, of a causal relationship between the local and remote data stores for a given data item is used to determine whether or not a conflict exists and/or whether a requested operation may be performed. The causal relationship may be determined using a previous commit's hash value, referred to as a hash_base value, and a hash value, both of which are associated with the data item.

Abstract: Images are optimized to reduce latency prior to being transmitted to requesting client devices. A request from a client device for an image is analyzed to obtain the attributes of the requesting client device and the network used by the client device for transmitting the request. The parameters of the image to be transmitted are determined based on the attributes in order to reduce data latency at the requesting client device. A requested image that meets the parameters or which has its parameters preset by a provider can be transmitted without any changes. A requested image that does not meet the parameters is transformed in accordance with the parameters so that it is optimized for the combination of the network and the requesting client device.