Abstract: Systems and methods permit or cause content to be displayed by a plurality of gaming displays, such as gaming machine displays and/or external displays. Content may be synchronously displayed by multiple gaming displays, such as one or more EGM displays and one or more external gaming displays, where the content which is displayed by the different displays may be the same or be different, and may be provided by a content controller and/or may be provided or triggered by a gaming machine. The systems and methods permit or cause content to be synchronously displayed across multiple gaming displays, such as in time and/or space. In some examples, the content is configured as a content “package” which is associated with one or more displays.

Abstract: The invention provides a one-step process for preparing a cell-binding agent cytotoxic agent conjugate comprising contacting a cell-binding agent with a cytotoxic agent to form a first mixture comprising the cell-binding agent and the cytotoxic agent and contacting the first mixture comprising the cell-binding agent and the cytotoxic agent with a bifunctional crosslinking reagent, which provides a linker, in a solution having a pH of about 4 to about 9 to provide a second mixture comprising the cell-binding agent cytotoxic agent conjugate, wherein the cell-binding agent is chemically coupled through the linker to the cytotoxic agent, free cytotoxic agent, and reaction by-products. The second mixture is then optionally subjected to purification to provide a purified cell-binding agent cytotoxic agent conjugate.

Abstract: Disclosed herein are glucosyltransferases with modified amino acid sequences. Such engineered enzymes exhibit improved alpha-glucan product yields and/or lower leucrose yields, for example. Further disclosed are reactions and methods in which engineered glucosyltransferases are used to produce alpha-glucan.

Abstract: A glass substrate comprises: a first surface with surface features having an average width, an average height, a ratio of the average height to the average width of from about 0.04 to about 0.24, and the first surface has a haze value of 3% to 40%. The glass substrate can be transparent to electromagnetic radiation in the visible spectrum. The glass substrate can have a composition of: 61-75 mol. % SiO2; 7-15 mol. % Al2O3; 0-12 mol. % B2O3; 9-21 mol. % Na2O; 0-4 mol. % K2O; 0-7 mol. % MgO; and 0-3 mol. % CaO. The first surface can have an average surface roughness Ra of from 10 nm to 1,000 nm. The first surface can have an average characteristic largest feature size of from 200 nm to 50 ?m. The ratio of the average height to the average width can be from 0.06 to about 0.08.

Abstract: A bowl assembly for a micro puree machine including an inner beaker and an outer bowl. The inner beaker is configured to receive ingredients and has an exterior bottom surface that includes a beaker alignment feature. The outer bowl is configured to receive the inner beaker therein. The outer bowl includes an interior bottom surface that includes a bowl alignment feature and an exterior bottom surface that includes a bowl securing element. The beaker alignment feature of the inner beaker exterior bottom surface is complementary to the bowl alignment feature of the outer bowl interior bottom surface such that, at times the inner beaker is positioned in the outer bowl, the complementary bowl alignment feature and inner beaker alignment feature prevent rotation of the inner beaker relative to the outer bowl. The bowl securing element is configured to receive and attach to a platform of a micro puree machine.

Abstract: Implementations include providing travel assistance services via a mobile device to dispatch a travel assistance vehicle to a user and transport the user to a safe destination. For example, a user of the travel assistance system may desire to be removed from a potentially dangerous situation, such as when traveling internationally in which the user may be unable to contact the authorities directly. The travel assistance system may be accessed by the mobile device in response to a situation for which a user may request a type of travel assistance response, such as a travel assistance vehicle or instructions on navigating a potentially unsafe situation. A travel assistance response may be provided based on information obtained from the mobile device, secondary information from databases, and/or a user profile. A risk assessment of the situation may be calculated by the system to determine the travel assistance response.

Abstract: Described herein are systems and methods for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a REST proxy service component. The REST proxy service uses a service development kit for the distributed ledger to communicate with the distributed ledger, and can provide REST APIs for use by client applications to query through chaincodes, synchronously or asynchronously invoke transactions through the chaincodes, get transaction statuses, and get BCS proxy versions. The REST proxy service component can authenticate REST calls, and translate the REST calls into remote procedural calls, for use in interfacing with the distributed ledger. The REST proxy service component can further provide REST APIs that support the same functions which are provided by the BCS management console component, and provide a user interface for client applications to consume the BCS instance.

Abstract: In accordance with an embodiment, described herein is a system and method for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a management console component. The management console component can include a web application running in a script runtime environment, a plurality of backend of APIs for communicating with various nodes of the blockchain cloud service, and a plurality of client APIs configured to be invoked by a client application. The plurality of client APIs uses one or more of the plurality of backend APIs in provisioning the distributed ledger as a blockchain cloud service, and in managing the managing the blockchain cloud service.

Abstract: In accordance with an embodiment, described herein is a system and method for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a management console component. The management console component can include a web application running in a script runtime environment, a plurality of backend of APIs for communicating with various nodes of the blockchain cloud service, and a plurality of client APIs configured to be invoked by a client application. The plurality of client APIs uses one or more of the plurality of backend APIs in provisioning the distributed ledger as a blockchain cloud service, and in managing the managing the blockchain cloud service.

Abstract: An exemplary embodiment of the present invention provides an exosuit support system, comprising first and second orthotic interfaces, first and second members, and first and second actuators. The first and second orthotic interfaces can be configured to attach to left and right legs of a user, respectively. The first member can comprise a first end connected to the first orthotic interface and a second end connected to a portion of the system configured to be positioned proximate a right shoulder of the user. The second member can comprise a first end connected to the second orthotic interface and a second end connected to a portion of the system configured to be positioned proximate a left shoulder of the user. The first actuator can be configured to apply a first tension to the first member. The second actuator can be configured to apply a second tension to the second member.

Abstract: In accordance with an embodiment, described herein is a system and method for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a management console component. The management console component can include a web application running in a script runtime environment, a plurality of backend of APIs for communicating with various nodes of the blockchain cloud service, and a plurality of client APIs configured to be invoked by a client application. The plurality of client APIs uses one or more of the plurality of backend APIs in provisioning the distributed ledger as a blockchain cloud service, and in managing the managing the blockchain cloud service.

Abstract: In accordance with an embodiment, described herein is a system and method for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a management console component. The management console component can include a web application running in a script runtime environment, a plurality of backend of APIs for communicating with various nodes of the blockchain cloud service, and a plurality of client APIs configured to be invoked by a client application. The plurality of client APIs uses one or more of the plurality of backend APIs in provisioning the distributed ledger as a blockchain cloud service, and in managing the managing the blockchain cloud service.

Abstract: In accordance with an embodiment, described herein is a system and method for conditional call path monitoring in a distributed transactional middleware environment. A cache can be provided in local memory, for use by an agent in the reporting and aggregation of call path metrics. When the agent collects such metrics, it does not report them immediately to a system and application monitor (SAM) manager (e.g., Tuxedo System and Application Monitor, TSAM), but instead stores them in the cache, indexed by correlation ID (identifier). When a predefined condition is met at a participating node, that node propagates a corresponding correlation ID to other participating nodes, via the SAM manager. The other participating nodes can then search for the correlation ID in the cache, and report to the SAM manager metrics of call paths which meet the condition.

Abstract: In accordance with an embodiment, described herein is a system and method for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a management console component. The management console component can include a web application running in a script runtime environment, a plurality of backend of APIs for communicating with various nodes of the blockchain cloud service, and a plurality of client APIs configured to be invoked by a client application. The plurality of client APIs uses one or more of the plurality of backend APIs in provisioning the distributed ledger as a blockchain cloud service, and in managing the managing the blockchain cloud service.

Abstract: In accordance with an embodiment, described herein are systems and methods for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a REST proxy service component. The REST proxy service uses a service development kit for the distributed ledger to communicate with the distributed ledger, and can provide REST APIs for use by client applications to query through chaincodes, synchronously or asynchronously invoke transactions through the chaincodes, get transaction statuses, and get BCS proxy versions. The REST proxy service component can authenticate REST calls, and translate the REST calls into remote procedural calls, for use in interfacing with the distributed ledger. The REST proxy service component can further provide REST APIs that support the same functions which are provided by the BCS management console component, and provide a user interface for client applications to consume the BCS instance.

Abstract: Systems and methods for implementing a distributed ledger as a blockchain cloud service are provided. The blockchain cloud service can include nodes of the distributed ledger and a REST proxy service component. The REST proxy service uses a service development kit for the distributed ledger to communicate with the distributed ledger, and can provide REST APIs for use by client applications to query through chaincodes, synchronously or asynchronously invoke transactions through the chaincodes, get transaction statuses, and get BCS proxy versions. The REST proxy service component can authenticate REST calls, and translate the REST calls into remote procedural calls, for use in interfacing with the distributed ledger. The REST proxy service component can further provide REST APIs that support the same functions which are provided by the BCS management console component, and provide a user interface for client applications to consume the BCS instance.

Abstract: In accordance with an embodiment, described herein is a system and method for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a management console component. The management console component can include a web application running in a script runtime environment, a plurality of backend of APIs for communicating with various nodes of the blockchain cloud service, and a plurality of client APIs configured to be invoked by a client application. The plurality of client APIs uses one or more of the plurality of backend APIs in provisioning the distributed ledger as a blockchain cloud service, and in managing the managing the blockchain cloud service.

Abstract: In accordance with an embodiment, described herein is a system and method for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a management console component. The management console component can include a web application running in a script runtime environment, a plurality of backend of APIs for communicating with various nodes of the blockchain cloud service, and a plurality of client APIs configured to be invoked by a client application. The plurality of client APIs uses one or more of the plurality of backend APIs in provisioning the distributed ledger as a blockchain cloud service, and in managing the managing the blockchain cloud service.

Abstract: In accordance with an embodiment, described herein are systems and methods for implementing a distributed ledger a blockchain cloud service. The blockchain cloud service can include nodes of the distributed ledger and a REST proxy service component. The REST proxy service uses a service development kit for the distributed ledger to communicate with the distributed ledger, and can provide REST APIs for use by client applications to query through chaincodes, synchronously or asynchronously invoke transactions through the chaincodes, get transaction statuses, and get BCS proxy versions. The REST proxy service component can authenticate REST calls, and translate the REST calls into remote procedural calls, for use in interfacing with the distributed ledger. The REST proxy service component can further provide REST APIs that support the same functions which are provided by the BCS management console component, and provide a user interface for client applications to consume the BCS instance.

Abstract: In accordance with an embodiment, described herein is a system and method for conditional call path monitoring in a distributed transactional middleware environment. A cache can be provided in local memory, for use by an agent in the reporting and aggregation of call path metrics. When the agent collects such metrics, it does not report them immediately to a system and application monitor (SAM) manager (e.g., Tuxedo System and Application Monitor, TSAM), but instead stores them in the cache, indexed by correlation ID (identifier). When a predefined condition is met at a participating node, that node propagates a corresponding correlation ID to other participating nodes, via the SAM manager. The other participating nodes can then search for the correlation ID in the cache, and report to the SAM manager metrics of call paths which meet the condition.