Abstract: A light control film comprises a light input surface and a light output surface opposite the light input surface. Alternating transmissive regions and absorptive regions are disposed between the light input surface and the light output surface. The absorptive regions have an aspect ratio of at least 30 and the alternating transmissive region and absorptive regions have a relative transmission at a viewing angle of 0 degrees of at least 75%.

Abstract: A light control film is described comprising alternating transmissive regions and absorptive regions disposed between a light input surface and a light output surface. The absorptive regions have an aspect ratio of at least 30. In some embodiments, the alternating transmissive regions and absorptive regions have a transmission as measured with a spectrophotometer at a viewing angle of 0 degrees of at least 35, 40, 45, or 50% for a wavelength of the range 320-400 nm (UV) and/or at least 65, 70, 75, or 80% for a wavelength of the range 700-1400 nm (NIR). In another embodiment, the absorptive regions block light at the light input surface and light output surface and the maximum surface area that is blocked is less than 20% of the total alternating transmissive regions and absorptive regions. Also described are various optical communication systems comprising the light control films described herein and methods.

Abstract: A light control film comprises a light input surface and a light output surface opposite the light input surface; alternating transmissive regions and absorptive regions disposed between the light input surface and the light output surface, wherein the absorptive regions comprise a core having a first concentration, C1, of a light absorbing material sandwiched between cladding layers having a second concentration, C2, of the light absorbing material, wherein C2<C1, and wherein the cores have an aspect ratio of at least 20.

Abstract: Approaches for transparently interfacing with a third party version control system (VCS) are provided. In one approach, an enterprise application integration (EAI) system comprises an integrated development environment (IDE) client, a repository, an API, and an API implementation. The IDE client enables a user to develop one or more functional components that can be used or executed to derive one or more enterprise application functionalities. The repository interacts with the IDE client to save and access the one or more functional components. The API is invoked by the repository to interact with any VCS. The API implementation enables the repository, by way of invoking the API, to interact with a VCS, which is an external VCS that is not provided as part of the EAI system.

Abstract: Approaches for transparently interfacing with a third party version control system (VCS) are provided. In one approach, an enterprise application integration (EAI) system comprises an integrated development environment (IDE) client, a repository, an API, and an API implementation. The IDE client enables a user to develop one or more functional components that can be used or executed to derive one or more enterprise application functionalities. The repository interacts with the IDE client to save and access the one or more functional components. The API is invoked by the repository to interact with any VCS. The API implementation enables the repository, by way of invoking the API, to interact with a VCS, which is an external VCS that is not provided as part of the EAI system.