Abstract: Disclosed are a messaging system, apparatuses circuits and methods of operation thereof. A messaging client device is adapted to receive an impermanent message and to manage the received message in accordance with a message management policy associated with the message. An impermanent messaging server is adapted to validate said messaging client device as complying with message management policies prior to authorizing transmission of the message to said messaging client device.

Abstract: Virtual environments may be presented to a user with an inclusion of one or more applications, but many such techniques for integrating the applications with the virtual environment may exhibit disadvantages. For example, a two-dimensional “flat” rendering of the application may require a loss of visual depth, and/or may appear inconsistent; an immersive presentation that is mutually exclusive with the presentation of the virtual environment may achieve very limited integration; and a holographic presentation may appear incongruous. Such techniques may also increase presentation latency, with noticeable and significant consequences. Instead, the virtual environment may define an application region, and may notify the application of the application region and a perspective of the user within the virtual environment.

Abstract: A media gateway and method with a media session manager function, a media processor function, and a media session state datastore function. The functions are provided by one or more instantiations which allow for independent scalability of the functions in the media gateway.

Abstract: A messaging system configured to receive a message from a first mobile messaging client device, transmit to a second mobile messaging client device a notification of the presence of the message, receive a message attribute comprising an instruction to limit a functionality of the message, apply the message attribute to the message base on a message characteristic and update any existing corresponding message attribute, and transmit the message and the message attribute to the second mobile messaging client device where the message and the message attribute are stored in non-volatile memory at least until the second mobile messaging client device manages the message in accordance with the message attribute, wherein managing the message comprises limiting functionality of the message based on the message attribute, wherein the message attribute comprises a predetermined message viewing time after which the message content cannot be accessed at the second mobile messaging client device.

Abstract: A packet processing system comprises a packet processing graph comprising classifier nodes including a root classifier node and leaf classifier nodes. The root classifier node is connected to each of the classifier nodes through a respective packet processing path in the graph. Each classifier node stores node match data indicative of at least one match to be applied by the respective classifier node. The classifier nodes comprise first and second classifier nodes arranged in a first packet processing path of said plurality of packet processing paths. The first classifier node stores node match data indicative of a match corresponding to content from a plurality of packet header field types, including first and second, different packet header field types. The second classifier node stores node match data indicative of a match corresponding to content from at least one packet header field type, including the first packet header field type.

Abstract: Embodiments of the present disclosure relate to software-defined networks, and particularly, but not exclusively to programmable packet data processing systems, methods and computer readable products for use therein.

Abstract: A graph data structure for a packet processing system is generated. The structure comprises graph data objects representing classifier nodes of a packet processing graph. The classifier nodes include a root node and leaf nodes. The root node is connected to each of the leaf nodes through respective corresponding packet processing paths through the graph. Each graph data object includes node match data indicative of at least one match to be applied by the respective classifier node. One or more n-type match graph data objects are identified, which include node match data indicative of an n-type match corresponding to content from n header field types. One or more (n+m)-type match graph data objects are identified, which include node match data indicative of an (n+m)-type match corresponding to a combination of content from a (n+m) different header field types. n and m are integer values of 1 or more.

Abstract: Measures, including methods, systems and non-transitory computer-readable storage mediums, for providing a Domain Name Service (DNS) configuration service for one or more network services provided in a cloud environment. Update data relating to one or more relationship updates that have occurred in at least one of the one or more network services is received. The one or more relationship updates relate to one or more service provision units in a cluster of service provision units deployed in the cloud environment to provide the at least one network service. DNS policy configuration data associated with the at least one network service is identified. On the basis of the identified DNS policy configuration data, data in a DNS configuration data database is updated.

Abstract: Object sets are often organized and traversed in a hierarchical manner according to ownership, wherein a subset of contained objects are processed before or after a containing object that contains the contained objects. Such object sets may also be presented as a scene, which may involve traversing the object set in a drawing order, such as a descending distance order that renders objects in a back-to-front manner. It may be difficult to reconcile these distinct traversal techniques, particularly if different portions of the object set utilize a different traversal order. Presented herein are hybrid traversal techniques in which a selected subset of related objects is identified and traversed in a drawing order, and the remainder of the object set is traversed in an ownership order, in furtherance of various tasks that involve hybrid traversal orders and/or to facilitate the traversal of different types of object subsets within the object set.

Abstract: A scene may be rendered as objects that are lit by various light sources. A scene designer may arrange the scene to create particular lighting effects when viewed from an initial perspective, such as gloss, translucency, and iridescence, and may choose lighting effects to create a desired aesthetic tone and/or highlighting within the scene. However, rendering the scene from a different perspective may alter the lighting effects (e.g., losing or misplacing desired lighting effects, and/or creating new and undesirable lighting effects, such as glare). Instead, when the scene is rendered from the initial perspective, the lighting effects created therein may be stored with the scene representation of the scene. A second rendering of the scene from a different perspective may reapply the stored lighting effects to the lit objects, thereby maintaining the lighting effects and the intent of the designer in the presentation of the scene from a different perspective.

Abstract: A method for managing a messaging system for receiving at a messaging server a message addressed, storing the message, transmitting a notification of the presence of the message at the messaging server, receiving a request to retrieve the message, validating the first mobile messaging client device, transmitting the message and a message attribute from the messaging server to the first mobile messaging client device, and receiving at the messaging server from the first mobile messaging client device a message management notification generated by the first mobile messaging client device in connection with managing the message in accordance with the message attribute at the first mobile messaging client device.

Abstract: Measures for providing timer services in a network including a cluster of nodes responsible for providing timer services to clients. At a given node in the cluster, a request to provide a timer is received from a client. Configuration of a primary replica of the requested timer on a first node in the cluster to pop after a first time has elapsed is initiated. A first timer replication message is transmitted to a second node in the cluster, the first timer replication message indicating that the second node should configure a first backup replica of the requested timer. A second timer replication message is transmitted to a third node in the cluster, the second timer replication message indicating that the third node should configure a second backup replica of the requested timer. Popping of the primary, first backup or second backup timer replicas includes initiating callback of a given client.

Abstract: A specimen testing system has holders that hold a specimen for testing. The holders brace the specimen so that a load may be applied. A load applicator applies a load to the specimen at a location that is between the holders bracing the specimen. A user may adjust the load applicator until it applies the desired load to the specimen. If desired, a user may apply rotation to a specimen while it is experiencing a load by using a specimen rotation system. The user may continue to adjust the load applied to the specimen or continue to rotate the specimen during loading until the specimen fails.

Abstract: A messaging system configured to receive a message from a first mobile messaging client device, transmit to a second mobile messaging client device a notification of the presence of the message, receive a message attribute comprising an instruction to limit a functionality of the message, apply the message attribute to the message base on a message characteristic and update any existing corresponding message attribute, and transmit the message and the message attribute to the second mobile messaging client device where the message and the message attribute are stored in non-volatile memory at least until the second mobile messaging client device manages the message in accordance with the message attribute, wherein managing the message comprises limiting functionality of the message based on the message attribute, wherein the message attribute comprises a predetermined message viewing time after which the message content cannot be accessed at the second mobile messaging client device.

Abstract: Land cultivating systems and methods utilizing high-pressure fluid jet cutting techniques are disclosed. An example system includes a mobile unit, a traveler arrangement operably coupled to the mobile unit to ride on the surface of stubble residues as the mobile unit moves across land to be cultivated, and a fluid jet cutting head supported by the traveler arrangement. The cutting head is configured to selectively discharge a high-pressure fluid jet to make a cut through the stubble residues and underlying soil as the mobile unit moves across the land. A soil opening device is provided to form a furrow in the ground in line with the cut made by the high-pressure fluid jet, and a liquid injector nozzle is provided to discharge fertilizer or other chemical(s) into the soil.

Abstract: A method for managing a messaging system for receiving at a messaging server a message addressed, storing the message, transmitting a notification of the presence of the message at the messaging server, receiving a request to retrieve the message, validating the first mobile messaging client device, transmitting the message and a message attribute from the messaging server to the first mobile messaging client device, and receiving at the messaging server from the first mobile messaging client device a message management notification generated by the first mobile messaging client device in connection with managing the message in accordance with the message attribute at the first mobile messaging client device.

Abstract: A messaging system including a server configured to receive a message from a second messaging device, transmit to a first messaging device a notification of the presence of the message at the server, transmit the message and a message attribute to the first messaging device, where the message and the message attribute are stored in non-volatile memory in the first messaging device at least until the message is managed by the first messaging device in accordance with the message attribute, and wherein the message attribute comprises a predetermined message viewing time after which at least a portion of the message cannot be displayed at the first messaging device, and receive from the first messaging device a message management notification generated by the first messaging device in connection with managing the message in accordance with the message attribute at the first messaging device.

Abstract: Objects in a computing environment are often utilized by threads through an object lifecycle, and are destroyed at the end of the object lifecycle to reclaim the computing resources used by the object. In some cases, a thread that initiates an object destruction of an object may be unable to complete the destruction (e.g., a second thread may hold a synchronization lock over an object resource of the object). An object destruction workflow initiates the destruction of an object on behalf of a thread. If the object destruction workflow encounters a failure to complete the object destruction, a new reference to the object is inserted into an object destruction list, as the last reference to the object. A second thread discovers and releases the last reference in the object destruction list, prompting the object destruction workflow to resume the attempt to destroy the object on behalf of the second thread.

Abstract: Measures, including methods, systems and non-transitory computer-readable storage mediums, for providing a Domain Name Service (DNS) configuration service for one or more network services provided in a cloud environment. Update data relating to one or more relationship updates that have occurred in at least one of the one or more network services is received. The one or more relationship updates relate to one or more service provision units in a cluster of service provision units deployed in the cloud environment to provide the at least one network service. DNS policy configuration data associated with the at least one network service is identified. On the basis of the identified DNS policy configuration data, data in a DNS configuration data database is updated.

Abstract: A messaging system configured to receive a message from a first mobile messaging client device, transmit to a second mobile messaging client device a notification of the presence of the message, receive a message attribute comprising an instruction to limit a functionality of the message, apply the message attribute to the message based on a message characteristic and update any existing corresponding message attribute, and transmit the message and the message attribute to the second mobile messaging client device where the message and the message attribute are stored in non-volatile memory at least until the second mobile messaging client device manages the message in accordance with the message attribute, wherein managing the message comprises limiting functionality of the message based on the message attribute, wherein the message attribute comprises a predetermined message viewing time after which the message content cannot be accessed at the second mobile messaging client device.