An approach for selective dynamic disabling of transport layer handshake spoofing is provided. A local proxy node of a communications network receives request message from a respective local host for establishing a network connection with a remote host. A destination address for the network connection is determined. It is determined whether the destination address is included in a handshake spoofing bypass list. If it is determined that the destination address is included in the spoofing bypass list, a corresponding un-spoofed connection request message is transmitted to a remote proxy node associated with the remote host, in accordance with a respective handshaking protocol for the connection establishment. If it is determined that the destination address is not included in the spoofing bypass list, a corresponding spoofed connection request message is transmitted to the remote proxy node, in accordance with a respective handshake spoofing protocol for the connection establishment.

The invention refers to a system for real-time resource consumption control in a distributed environment and a corresponding method, the system comprising: a multitude of server instances (Sx) having access to shared resources, whereby each request for a shared resource issued by a client application (CA) is handled by one of the server instances (Sx); a global resource consumption counter (G), representing the overall resource consumption of the multitude of server instances (Sx) at a given time; and a multitude of proxy servers (Lx), each proxy server comprising—a receiver module (R) for receiving resource consumption requests issued from a client application (CA), a resource consumption decision module (Dm) for accepting or rejecting a resource consumption request, a queue (Q) for collecting resource consumption requests that have been locally accepted by the respective proxy server (Lx), a local resource consumption counter (L), representing the global resource consumption as seen by the respective proxy server (Lx), said local resource consumption counter (L) being updated every time a resource consumption request is accepted by the decision module (Dm), the updated value being provided in turn as an input to the decision module (Dm), and a synchronization module (S) for synchronizing the global resource consumption counter (G) by interfacing with all other server instances (Sx).

In general, this disclosure is directed to techniques for sending notification data to computing devices that are unable to receive the notification data from a central server. A server device may receive notification data for a notification account that is associated with a computing device and determine that the computing device is currently offline. The server device may then identify a group of one or more sharing devices and send a notification package to a sharing device of the group, wherein the notification package includes the notification data, an account identifier associated with the notification account, and a device identifier associated with the computing device. The sharing device may receive the notification package and, responsive to determining that a device identifier for the computing device matches the device identifier in the notification package, forward the notification data to the computing device.

An extended service-function chain (SFC) proxy is hosted on a network node and connected to a service path formed by one or more network nodes hosting a chain of service-functions applied to packets traversing the service path. The packets each include a service header having a service path identifier and a service index. A packet of a traffic flow destined for a service-function is received from the service path and sent to the service-function. An indication to offload the traffic flow is received from the service-function. The indication is stored in a flow table having entries each identifying a respective traffic flow. A subsequent packet of the traffic flow is received from the service path. The flow table is searched for the indication to offload the traffic flow. Upon finding the indication, the service-function is bypassed, and the subsequent packet is forwarded along the service path.

An extended service-function chain (SFC) proxy is hosted on a network node and connected to a service path formed by one or more network nodes hosting a chain of service-functions applied to packets traversing the service path. The packets each include a service header having a service path identifier and a service index. A packet of a traffic flow destined for a service-function is received from the service path and sent to the service-function. An indication to offload the traffic flow is received from the service-function. The indication is stored in a flow table having entries each identifying a respective traffic flow. A subsequent packet of the traffic flow is received from the service path. The flow table is searched for the indication to offload the traffic flow. Upon finding the indication, the service-function is bypassed, and the subsequent packet is forwarded along the service path.

A virtual desktop server include an application framework comprising a real-time media application to provide real-time communications (RTC), a native RTC engine to execute a portion of the real-time media application when received, and a processor coupled to the application framework and to the native RTC engine. The processor redirects original application program interfaces (APIs) of the real-time media application intended for the native RTC engine based on redirection code injected into the real-time media application so that the portion of the real-time media application is to be redirected. The processor receives from a client computing device capabilities of the client computing device to execute the redirected portion of the real-time media application. The processor switches to a fallback mode if the client computing device has limited capabilities.

A virtual desktop server include an application framework comprising a real-time media application to provide real-time communications (RTC), a native RTC engine to execute a portion of the real-time media application when received, and a processor coupled to the application framework and to the native RTC engine. The processor redirects original application program interfaces (APIs) of the real-time media application intended for the native RTC engine based on redirection code injected into the real-time media application so that the portion of the real-time media application is to be redirected. The processor receives from a client computing device capabilities of the client computing device to execute the redirected portion of the real-time media application. The processor switches to a fallback mode if the client computing device has limited capabilities.

A proxy management controller system includes a first management controller device in a first server device, a second management controller device in a second server device, and a proxy management controller manager subsystem coupled to the first and second management controller device. The first management controller device receives an instruction from the proxy management controller manager subsystem to provide a proxy management controller for the second management controller device, and creates a proxy management controller virtual container for the second management controller device. The first management controller device then receives raw data collected by the second management controller device from the second server device, stores the raw data in the proxy management controller virtual container, and converts the raw data to formatted data. The first management controller device then uses the formatted data to perform at least one management operation that is associated with the second management controller device.

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

Providing a distributed network service includes: receiving network traffic at a first physical device; and executing a service engine to participate in the distributed network service. The distributed network service is provided to at least the first target application instance executing in a first VM on the first physical device, and a second target application instance executing in a second VM on a second physical device; and a shared state of the distributed network service is maintained with respect to the first physical device and the second physical device.