Vmware, Inc.

Kiril Karaatanassov

Maya Ilieva

Mariana Valeva

Grigor Harbaliev

Radoslav Nikolov

One or more examples provide a method of performing a REST API operation at a server computing system includes receiving a request of a hypertext transfer protocol (HTTP) session from a client computing system. The request includes data for requesting performance of the REST API operation and issuance of progress updates. The method further includes sending a first part of a response of the HTTP session to the client computing system. The first part of the response acknowledges the request. The method further includes sending, while the REST API operation is performed, at least one additional part of the response to the client computing system, each additional part of the response having a progress update for the REST API operation. The method further includes sending, upon completion of the REST API operation, a final part of the response to the client computing system having a result of the REST API operation.

Streaming progress updates and results of rest API operations

The current document discloses methods and systems for providing extensions to web-services APIs, including RESTful APIs, and to extend other types of interfaces that define client/server-based distributed computing systems. The disclosed methods and systems are facilitated by, and include, respectively, a link registry within one or more server computers, or that is accessible to the one or more server computers, that together provide a web service accessed through an API. The link registry stores link-registry entries, each of which specifies one or more links to be added to response messages associated with a particular resource. The link registry, like any resource, is associated with a set of verbs, or functions, that allow entries to be added to, and removed from, the link registry and that allow entries to be modified. The link registry can be used both by server-resident functionality as well as by functionality within external computers to extend an existing web service or API.

Method and system for extending application programming interfaces

The current document is directed to an interface and authorization service that allows users of a cloud-director management subsystem of distributed, multi-tenant, virtual data centers to extend the services and functionalities provided by the cloud-director management subsystem. A cloud application programming interface ('API') entrypoint represents a request/response RESTful interface to services and functionalities provided by the cloud-director management subsystem as well as to service extensions provided by users. The cloud API entrypoint includes a service-extension interface and an authorization-service management interface. The cloud-director management subsystem provides the authorization service to service extensions that allow the service extensions to obtain, from the authorization service, an indication of whether or not a request directed to the service extension through the cloud API entrypoint is authorized.

Extensible multi-tenant cloud-management system and methods for extending functionalities and services provided by multi-tenant cloud-management system

A system is described allowing a user to log into an API proxy by supplying login credentials and to have the API proxy log into the APIs of various web-based applications on behalf of the user by using the user's login credentials, without the user needing to separately log into each application. Calls made by the user to an application and application replies are routed through the API proxy. Further, the API proxy manages session expirations, e.g., by sending dummy calls to applications that exhibit idle expiration.

Providing a single session experience across multiple applications

Extensible multi-tenant cloud-management system and methods for extending functionalities and services provided by a multi-tenant cloud-managment system

Growing community of inventors

Sofia, Bulgaria

Kiril Karaatanassov