A relay communication device includes a memory and a processor coupled to the memory and configured to: receive data from an application, and determine a relay path of each of a plurality of data received from the application according to a protocol of a disruption tolerant network based on data remaining amount to be relayed to a communication destination in response to receiving of new data of the application and a priority of each of the plurality of data.

Some embodiments establish for an entity a virtual network over several public clouds of several public cloud providers and/or in several regions. In some embodiments, the virtual network is an overlay network that spans across several public clouds to interconnect one or more private networks (e.g., networks within branches, divisions, departments of the entity or their associated datacenters), mobile users, and SaaS (Software as a Service) provider machines, and other web applications of the entity. The virtual network in some embodiments can be configured to optimize the routing of the entity's data messages to their destinations for best end-to-end performance, reliability and security, while trying to minimize the routing of this traffic through the Internet. Also, the virtual network in some embodiments can be configured to optimize the layer 4 processing of the data message flows passing through the network.

Methods and apparatus for efficient data transfer within a user space network stack. Unlike prior art monolithic networking stacks, the exemplary networking stack architecture described hereinafter includes various components that span multiple domains (both in-kernel, and non-kernel). For example, unlike traditional “socket” based communication, disclosed embodiments can transfer data directly between the kernel and user space domains. Direct transfer reduces the per-byte and per-packet costs relative to socket based communication. A user space networking stack is disclosed that enables extensible, cross-platform-capable, user space control of the networking protocol stack functionality. The user space networking stack facilitates tighter integration between the protocol layers (including TLS) and the application or daemon. Exemplary systems can support multiple networking protocol stack instances (including an in-kernel traditional network stack).

Network TCP tunnels are dynamically configured to support intra-application connectivity of a distributed application. Tunnel origins listen on each server's loopback address. This listening configuration permits only applications running on the same server to connect. A tunnel gateway application interfaces with the distributed application on each server and includes a tunnel endpoint manager configured to select one or more TCP ports. These selected ports are each associated with a separate TCP listeners. Once associated, data from the instance of the distributed application resident on each of the plurality of servers in the server cluster is routed through these TCP connections and a UDP datagram-orientated communication channel formed between each peer in the server cluster. Each instance of the distributed application can thereafter access peers in the server cluster through each unique UDP datagram-orientated communication channel.

A method comprises receiving at a compiler a bit file description and a program, said bit file description comprising a description of routing of a part of a circuit. The method comprises compiling the program using said bit file description to output a bit file for said program.

A method is disclosed comprising: instantiating a first plurality of type-1 network sockets on a source computing system, each of the type-1 network sockets having a first queue depth; instantiating a second plurality of type-2 network sockets on the source computing system, each of the type-2 network sockets having a second queue depth that is greater than the first queue depth; transitioning the source computing system into a first state, the first state being one in which data replication messages are transmitted by the source computing system to a target computing system by using both the type-1 and type-2 network sockets; transitioning the source computing system from the first state into a second state, the second state being one in which data replication messages are transmitted by the source computing system to the target computing system by using the type-2 network sockets.

Described herein is a computer-implemented collaborative editing system for editing of electronic resources including documents and other electronic information. The system includes: an editor interface for interfacing with an editor executing on a client device, the editor being configured to edit a resource; an editing identity module for causing the processing unit to store a designation of the client device as a privileged or a non-privileged editor; and an editing interface for causing the processing unit to: receive proposed edits to the resource from the editor interface and communicate the proposed edits to a remote collaborative editing service; receive remote proposed edits to the resource from the remote collaborative editing service and in the event that the client device is designated as a privileged editor, accept or reject the remote proposed edits and communicate the acceptance or rejection to the remote collaborative editing service.

Systems and methods for securely handling data traffic on local or private networks, such as by using cloud computing, are provided. A non-transitory computer-readable medium, according to one implementation, may be configured to store executable instructions enabling a processor of a user device to perform the step of discovering an origin of a source application associated with network packets bound for a private address space. The executable instructions may further enable the processor to send a tuple regarding the discovered origin to a cloud server to request an analysis of the tuple. Upon receiving an allow instruction from the cloud server, the instructions enable the processor to allow the network packets to flow normally to a destination associated with the private address space. Upon receiving a deny instruction from the cloud server, the instructions enable the processor to drop the network packets.

Methods and apparatus for active queue management in user space networking stacks. Unlike prior art monolithic networking stacks, the exemplary networking stack architecture described hereinafter includes various components that span multiple domains (both in-kernel, and non-kernel). For example, unlike traditional “socket” based communication, disclosed embodiments can transfer data directly between the kernel and user space domains. Additionally, user space networking stacks require a new flow control methodology that is responsive to networking congestion and/or packet loss. For example, embodiments of the present disclosure introduce a flow advisory table that may, for example, utilize an eventing methodology for active queue management in addition to, or alternatively then, legacy active queue management. Exemplary systems can support multiple networking protocol stack instances (including an in-kernel traditional network stack) as well as flow advisory tables (and legacy active queue management).

This disclosure describes techniques for providing multiple namespace support to application(s) in containers under Kubernetes without breaking containment boundaries or escalating privileges of the application(s). A namespace service executing on a physical server may communicate with contained processes executing on the physical server by utilizing a Unix Domain Socket (UDS) endpoint in the filesystem of each of the containers. the namespace service may execute on the physical server with escalated privileges, allowing the namespace service to create a socket in a namespace and provide access and rights to utilize the socket to process(es) in a separate namespace.