Abstract:
Techniques to share binary content are described. An apparatus may comprise a first related client having a message platform with a file share feature and an object store, the file share feature operative to retrieve a data object for a publishing client having a defined relationship with the first related client and a second related client, the first related client to send the data object to the second related client on behalf of the publishing client, and the object store operative to store and manage the data object using a unique name identifier received with the data object. Other embodiments are described and claimed.
Abstract:
One or more techniques and/or systems are provided for processing data requests received over various communication protocols. In particular, a data transfer component may be configured to process data requests and/or responses between requesting devices and data handlers utilizing various communication protocols (e.g., peer-to-peer communication protocols, web based communication protocols, etc.). In particular, communication protocol functionality may be abstracted away from the data handlers, and may be handled by the data transfer component. In this way, data handlers may be communication protocol agnostic because the data transfer component may perform the communication protocol functionality on behalf of the data handlers, which may allow the data handlers to be more “lightweight” and focus primarily on fetching and/or formatting requested data.
Abstract:
Reliable communication may be implemented using various underlying transport mechanisms, where the underlying transport mechanisms may be reliable or non-reliable. When data is sent from a source to a destination, the source may sent acknowledgment requests (RACKs) to the destination, and may await acknowledgments (ACKs) from the destination. The RACKs and ACKs are sent over the underlying transport mechanism. The rate at which the data source requests acknowledgments from the destination may be varied, depending on the underlying transport mechanism, to achieve lower overhead and to optimize throughput. For example, RACKs may be sent relatively less frequently when the underlying mechanism implements guaranteed delivery, and may be sent relatively more frequently when the underlying transport does not provide guaranteed delivery.
Abstract:
One or more techniques and/or systems are provided for processing data requests received over various communication protocols. In particular, a data transfer component may be configured to process data requests and/or responses between requesting devices and data handlers utilizing various communication protocols (e.g., peer-to-peer communication protocols, web based communication protocols, etc.). In particular, communication protocol functionality may be abstracted away from the data handlers, and may be handled by the data transfer component. In this way, data handlers may be communication protocol agnostic because the data transfer component may perform the communication protocol functionality on behalf of the data handlers, which may allow the data handlers to be more “lightweight” and focus primarily on fetching and/or formatting requested data.
Abstract:
A connectivity automation tool provides a robust, general and reusable platform that enables programs to communicate in a variety of connectivity environments. Applications, such as automated tests, can rely on this tool for testing under various connectivity environments. In accordance with at least some embodiments, the connectivity automation tool enables connectivity testing to be fully automated, thus reducing the resources required to carry out connectivity testing and increasing the number of connectivity scenarios that can be covered.
Abstract:
Techniques to share binary content are described. An apparatus may comprise a first related client having a message platform with a file share feature and an object store, the file share feature operative to retrieve a data object for a publishing client having a defined relationship with the first related client and a second related client, the first related client to send the data object to the second related client on behalf of the publishing client, and the object store operative to store and manage the data object using a unique name identifier received with the data object. Other embodiments are described and claimed.
Abstract:
Reliable communication may be implemented using various underlying transport mechanisms, where the underlying transport mechanisms may be reliable or non-reliable. When data is sent from a source to a destination, the source may sent acknowledgment requests (RACKs) to the destination, and may await acknowledgments (ACKs) from the destination. The RACKs and ACKs are sent over the underlying transport mechanism. The rate at which the data source requests acknowledgments from the destination may be varied, depending on the underlying transport mechanism, to achieve lower overhead and to optimize throughput. For example, RACKs may be sent relatively less frequently when the underlying mechanism implements guaranteed delivery, and may be sent relatively more frequently when the underlying transport does not provide guaranteed delivery.