A computing device, running a web browser, can listen for an event on the web browser that is operated by a first user. In response to an occurrence of a first event, the computing device can obtain, through the web browser a URL or content of a web page being visited by the web browser. The computing device can obtain a unique identifier that is uniquely associated with a second user, based on the second user belonging to a network of users that is associated with the first user, and based on whether the unique identifier is applicable to the URL or the web page that is open in the browser. The computing device can present the unique identifier to the first user through the web browser.

Embodiments described herein are generally directed to improving performance of a transactional API protocol by batch scheduling data dependent functions. In an example, a prescribed sequence of function calls associated with a transactional application programming interface (API) is received that is to be carried out by an executer (e.g., a compute service or a second processing resource remote from a first processing resource with which an application is associated) to perform an atomic unit of work on behalf of the application. Transport latency over an interconnect between the application and the executer is reduced by: (i) creating a batch representing the prescribed sequence of function calls in a form of a list of function descriptors in which variable arguments of the prescribed sequence of function calls are replaced with corresponding global memory references; and (ii) transmitting the batch via the interconnect as a single message.

A method, a system and a computer program product for hybrid computing system management are proposed. In the method, workload information associated with a set of application server instances running in a first computing system is obtained by a server controller in response to a scaling request for changing the number of instances in the set of application server instances from a request controller. The set of application server instances serves at least one application running in a second computing system. A scaling decision indicating whether to change the number of instances in the set of application server instances is determined by a predictor based on the workload information from the server controller. The second computing system is enabled by the request controller to handle requests associated with the at least one application for the set of application server instances based on the scaling decision.

In one embodiment, a method comprises: receiving, by a secure executable container executed by a network device, a request initiated by a user for a community forum in a secure data network, the user having generated the request via an endpoint device and the user having established a two-way trusted relationship with the endpoint device in the secure data network; processing, by the secure executable container, the request for the community forum in the secure data network, the processing including causing a network device executing a community server to post the community forum in the secure data network according to identifiable features selected by the user; and preventing, by the secure executable container, any executable resource in the network device from accessing the secure data network without authorized access via a prescribed Application Programming Interface (API) required by the secure executable container.

Techniques for an application programming interface (API) notebook tool are disclosed. In some implementations, an API notebook is a tool, framework, and ecosystem that enables easy exploration of services that expose APIs, creation and documentation of examples, use cases and workflows, and publishing and collaboration of APIs. In some embodiments, systems, processes, and computer program products for an API notebook tool include receiving a request for a client for calling an API for a service, and dynamically generating the client for the API for the service.

Aspects of a cloud service framework are described. In some examples, a noncompliance event is received. The noncompliance event is identified using parameters detected from a deployment of hardware resources and software resources provided by a cloud service according to a service level agreement (SLA). An application programming interface (API) associated with the noncompliance event is identified. The API is disabled by updating an API availability status. A request to invoke the API is received, and the API is prevented from being forwarded to a backend service that provides the API.

A computer program product, system, and computer-implemented method for facilitating co-browsing of a web application wherein HTML and JavaScript code within a web application are wrapped and brokered to a plurality of third parties.

Embodiments of a device and method are disclosed. In an embodiment, a method for network device authentication involves using Remote Procedure Call (RPC) proxies of network devices of a network at a customer site, accessing identity certificates from Trusted Platform Modules (TPMs) of the network devices, and using the RPC proxies, sequentially establishing Transport Layer Security (TLS) connections between the network devices to perform mutual authentication between the network devices based on the identity certificates.

A method, computerized apparatus and computer program product, the method comprising: obtaining user code; using static analysis, determining from the user code a collection of components upon which the user code depends, the collection of components comprising a first component representing a first entity, wherein one or more components of the collection of components is to be loaded dynamically by the user code; determining whether the user code or the first component from the collection of components uses dynamic invocation; subject to the user code or the first component using dynamic invocation, adding a new connection to a second component from the collection of components, the second component representing a second entity that augments an entity reachable from the first entity; and outputting information about the second entity.

The disclosure relates to processing application programming interface (API) requests. Embodiments include receiving, at an API wrapper, from a first caller, a first call to an API and sending the first call to the API. Embodiments include receiving, by the API wrapper, from one or more second callers, a second one or more calls to the API prior to receiving a response from the API to the first call. Embodiments include receiving, by the API wrapper, the response from the API to the first call and responding to the first call from the first caller with the response from the API to the first call. Embodiments include responding, by the API wrapper, to the second one or more calls from the one or more second callers with the response from the API to the first call without sending the second one or more calls to the API.