Abstract: A smart power strip having a plurality of first electrical contacts along a surface adjacent a track along which a plurality of power plugs can be selectively slid and locked in place to form customized arrangements of different power plugs along the smart power strip. Each power plug provides one of the following power and data interfaces: two-prong power, three-prong power, USB, and HDMI interfaces along a first face thereof, and wherein along an opposing second face each power plug provides a plurality of second electrical contacts for operatively associating a subset of the first electrical contacts, whereby each power plug is selective controllable and readable by a software application. The present invention also provides one or more spacers which can be locked along the track to selectively space apart each interchangeable power plug.

Abstract: An optical sensor system may include optical fibers having at least one corresponding optical sensing element configured to reflect light; a laser configured to output light of a discrete wavelength and to change the discrete wavelength through a sequence; an optical network connecting the laser to the optical fibers, and configured to split the output light so that a split portion of the output light is transmitted through an optical fiber of the optical fibers to the at least one corresponding optical sensing element which may reflect at least a portion of the split portion; an optical sensor configured to obtain information about of the reflected light and to output data corresponding to the information about the reflected light; and a processor configured to: obtain, from the optical sensor, the data corresponding to the information about the reflected light in correspondence with discrete wavelengths of the sequence.

Abstract: A magnetic coupling system that includes a first housing disposed about an end of a first conduit. The first housing includes an axially-extending annular flange. A first annular magnetic element, coupled to the first housing and concentric with the annular flange, has a first plurality of magnetic polarities disbursed thereabout. A second housing, disposed about an end of a second conduit, includes an axially-extending annular channel for engagement with the annular flange. A second annular magnetic element is coupled to the second housing and is concentric with the annular channel. An air gap is disposed between the first annular magnetic element and the second annular magnetic element when the annular flange is engaged in the annular channel. The second annular magnetic element has a second plurality of magnetic polarities disbursed thereabout.

Abstract: A vehicle receives a vehicle data package including instructions for use of one or more vehicle outputs to behave in a preconfigured manner, indicated in the data package, based on the occurrence of a trigger condition, also included in the data package. The vehicle monitors at least temporal or vehicle states corresponding to the trigger condition until state values indicate occurrence of the trigger conditions and, responsive to occurrence of the trigger condition, automatically utilizes the one or more vehicle outputs to output a coordinated sequence of events indicated in the data package.

Abstract: A layer of abstraction is provided for developing, configuring, displaying, selecting, and re-configuring connectors used through stages of predeployment, deployment, and post-deployment. A connector is created with the layer of abstraction, wherein the connector provides a first configuration of added functionality to software components for calling a web service. The connector is used to tie a step of a process-based software application to the web service. A different configuration of added functionality is provided for each of the stages of predeployment, deployment, and post deployment using the layer of abstraction.

Abstract: A layer of abstraction is provided for developing, configuring, displaying, selecting, and re-configuring connectors used through stages of predeployment, deployment, and post-deployment. A connector is created with the layer of abstraction, wherein the connector provides a first configuration of added functionality to software components for calling a web service. The connector is used to tie a step of a process-based software application to the web service. A different configuration of added functionality is provided for each of the stages of predeployment, deployment, and post deployment using the layer of abstraction.

Abstract: An example system and method facilitates customization of and configuration of a software connector, such as a connector to an Application Programming Interface (API) or web service, in various types of computing environments, including both pre-deployment and post-deployment computing environments. A connectors framework provides a layer of abstraction between connectors maintained in the different environments and a connector editor of an application development system (which may be implemented via a server-side integrated development environment). The connector editor may provide User Interface (UI) functionality, including one or more UI controls for editing or otherwise modifying, customizing, and/or configuring connectors in pre-deployment and/or post deployment environments, which may represent or correspond to different connector and accompanying software development stages.

Abstract: Implementations provide a database lock mechanism used to prevent concurrent writes to service on network partition scenarios associated with a version control system. The database lock mechanism may be provided on per repository basis to ensure both nodes are working and maintaining data consistency, even when they are not connected when interruptions in network communication disrupts the intercommunication between nodes. In other implementations, the disclosed locking mechanism is configured to ensure and perform write and synchronization operations on isolated nodes, regardless of miss-communication between the nodes.

Abstract: In one implementation, lightweight incremental backups are created by a data recovery tool, which provides an extra layer of protection against data loss, and also provides a way of moving repositories between databases without the need of copying each of the repositories. Implementations include backing up a distributed cluster of services providing a simple, safe, and convenient way of instantiating files system repositories in a database, thereby avoiding the performance and scalability issues of using a database repository itself. In other implementations, a lightweight backup object is created that includes a threshold amount of compressed information. The lightweight backup objects may be configured to provide the differences between revisions, and/or may be configured to replicate or rebuild the repository from scratch. Implementations may be configured to backup and restore any single or revision set in any repository state either online or offline.

Abstract: Implementations described herein provide a bidirectional tool configured to provide APIs to enable a cross-cluster service handshakes and design and implementation for enabling two or more instances of an application registered to one cluster and other cluster provides for multi environment interaction. Using a common service registration, users can trigger actions on different instances of the application running in different environments such as a development environment, production environment, and the like. Using the common registration, applications can scale by having extra instances running while a centralized service works as central hub were each instance is registered. Moreover, implementations include utilizing a plurality of deployment asset management layers to establish a stateless API instantiated between point-of-delivery server arrays employed to house multiple customers separated by security partitions.

Abstract: A power stealing system having an electrical load, a capacitive element having an input connected to the electrical load. Some power from the electrical load may go through the capacitive element to an input of a rectifier. A voltage regulator may have an input connected to an output of the rectifier to set and control a voltage level of the electrical power from the rectifier, and provide an output of power stolen from the electrical load. An amount of power flowing through the capacitive element may be less than one percent of power flowing through the electrical load.

Abstract: An example system and method facilitates customization of and configuration of a software connector, such as a connector to an Application Programming Interface (API) or web service, in various types of computing environments, including both pre-deployment and post-deployment computing environments. A connectors framework provides a layer of abstraction between connectors maintained in the different environments and a connector editor of an application development system (which may be implemented via a server-side integrated development environment). The connector editor may provide User Interface (UI) functionality, including one or more UI controls for editing or otherwise modifying, customizing, and/or configuring connectors in pre-deployment and/or post deployment environments, which may represent or correspond to different connector and accompanying software development stages.

Abstract: A power stealing system having an electrical load, a capacitive element having an input connected to the electrical load. Some power from the electrical load may go through the capacitive element to an input of a rectifier. A voltage regulator may have an input connected to an output of the rectifier to set and control a voltage level of the electrical power from the rectifier, and provide an output of power stolen from the electrical load. An amount of power flowing through the capacitive element may be less than one percent of power flowing through the electrical load.

Abstract: Implementations provide a database lock mechanism used to prevent concurrent writes to service on network partition scenarios associated with a version control system. The database lock mechanism may be provided on per repository basis to ensure both nodes are working and maintaining data consistency, even when they are not connected when interruptions in network communication disrupts the intercommunication between nodes. In other implementations, the disclosed locking mechanism is configured to ensure and perform write and synchronization operations on isolated nodes, regardless of miss-communication between the nodes.

Abstract: An example system and method facilitates customization of and configuration of a software connector, such as a connector to an Application Programming Interface (API) or web service, in various types of computing environments, including both pre-deployment and post-deployment computing environments. A connectors framework provides a layer of abstraction between connectors maintained in the different environments and a connector editor of an application development system (which may be implemented via a server-side integrated development environment). The connector editor may provide User Interface (UI) functionality, including one or more UI controls for editing or otherwise modifying, customizing, and/or configuring connectors in pre-deployment and/or post deployment environments, which may represent or correspond to different connector and accompanying software development stages.

Abstract: Implementations provide a database lock mechanism used to prevent concurrent writes to service on network partition scenarios associated with a version control system. The database lock mechanism may be provided on per repository basis to ensure both nodes are working and maintaining data consistency, even when they are not connected when interruptions in network communication disrupts the intercommunication between nodes. In other implementations, the disclosed locking mechanism is configured to ensure and perform write and synchronization operations on isolated nodes, regardless of miss-communication between the nodes.

Abstract: Implementations described herein provide a bidirectional tool configured to provide APIs to enable a cross-cluster service handshakes and design and implementation for enabling two or more instances of an application registered to one cluster and other cluster provides for multi environment interaction. Using a common service registration, users can trigger actions on different instances of the application running in different environments such as a development environment, production environment, and the like. Using the common registration, applications can scale by having extra instances running while a centralized service works as central hub were each instance is registered. Moreover, implementations include utilizing a plurality of deployment asset management layers to establish a stateless API instantiated between point-of-delivery server arrays employed to house multiple customers separated by security partitions.

Abstract: Implementations described herein provide a bidirectional tool configured to employ application program interfaces (APIs), cross-cluster service handshakes, and design and implementation enabling two or more instances of an application registered to one cluster and other clusters to provide multi environment interaction. Using a common service registration, users can trigger actions on different instances of the application running in different environments such as a development environment, production environment, and the like. Using the common registration, applications can scale by having extra instances running while a centralized service works as central hub were each instance is registered. Moreover, implementations include utilizing a plurality of deployment asset management layers to establish a stateless API instantiated between point-of-delivery server arrays employed to house multiple customers separated by security partitions.

Abstract: An example system and method facilitates customization of and configuration of a software connector, such as a connector to an Application Programming Interface (API) or web service, in various types of computing environments, including both pre-deployment and post-deployment computing environments. A connectors framework provides a layer of abstraction between connectors maintained in the different environments and a connector editor of an application development system (which may be implemented via a server-side integrated development environment). The connector editor may provide User Interface (UI) functionality, including one or more UI controls for editing or otherwise modifying, customizing, and/or configuring connectors in pre-deployment and/or post deployment environments, which may represent or correspond to different connector and accompanying software development stages.

Abstract: Implementations provide a database lock mechanism used to prevent concurrent writes to service on network partition scenarios associated with a version control system. The database lock mechanism may be provided on per repository basis to ensure both nodes are working and maintaining data consistency, even when they are not connected when interruptions in network communication disrupts the intercommunication between nodes. In other implementations, the disclosed locking mechanism is configured to ensure and perform write and synchronization operations on isolated nodes, regardless of miss-communication between the nodes.