US 11,455,175 B2 · Transparently remote execution of development tool extensions

Abstract

Enhancements described support transparent remote execution of development tool extensions. Compute-intensive extensions may be executed on an extension machine external to a developer machine which runs a user interface renderer of the development tool. User interface extensions may run locally. Instead of sharing a filesystem, the renderer on the developer machine and an extension host and extension(s) on the extension machine may access distinct respective machine filesystems. Instead of spawning debug extension and other extension-support processes locally, the renderer may instruct the extension host or an extension host agent to spawn the processes remotely on the extension machine. Existing extensions and newly created extensions are binary-compatible with single-machine or multi-machine development tool deployments. Project files remain inside a firewalled and data-loss-prevention environment while being fully accessible to authorized developers working remotely and to operations performed by language servers, debug adapters, and tool extensions.

Claims20

Dependent claims

An extension machine suitable for use in a development tool system and configured to interoperate with a local development tool extension (“extension”) which upon execution on the extension machine performs software development operations on file contents, the extension machine comprising:

a processor;
a memory in operable communication with the processor;
a local extension host agent (“agent”) which upon execution with the processor communicates with a remote development tool user interface renderer (“renderer”) that resides on a developer machine external to the extension machine;
a local extension host (“host”) which is configured for operable communication with the local agent and with the local extension and with a local store which has a filesystem containing software development files (“files”);
wherein multiple files in the local store are identified in at least one place outside the extension machine by respective uniform resource identifiers (“URI”) file IDs, and those URI file IDs get mapped to filesystem paths for use in the local extension to identify the files in order to obtain the file contents;
and
wherein the local extension host agent, local extension host, local agent, local extension, and local store are each local to the extension machine and remote from the developer machine.

4 more elements

A developer machine suitable for use in a development tool system and configured to interoperate with a remote development tool extension (“extension”) which upon execution performs software development operations on remote file contents, the developer machine comprising:

a processor;
a memory in operable communication with the processor;
a development tool user interface renderer (“renderer”) which upon execution with the processor communicates with the remote extension by sending and receiving inter-machine communications which identify one or more of the software development operations, the remote extension residing on an extension machine that is external to the developer machine, the renderer configured to use uniform resource identifiers (“URIs”) to identify files in a remote filesystem in a store on the extension machine;
wherein the renderer is further configured to specify in one or more of the inter-machine communications one or more development processes to be spawned remotely on the extension machine instead of the renderer spawning those development processes on the developer machine.

1 more element

Dependencies are inferred from the claim text.

Transparently remote execution of development tool extensions

Life of this patent

Transparently remote execution of development tool extensions

Life of this patent

Abstract

Claims20