Systems and methods for running applications associated with browser-based user interfaces within multi-developer computing platforms

Patent metadata

Field	Value
Publication number	US-11294694-B2
Application number	US-202016931663-A
Country	US
Kind code	B2
Filing date	Jul 17, 2020
Priority date	Jul 23, 2019
Publication date	Apr 5, 2022
Grant date	Apr 5, 2022

Abstract

Systems and methods for developing one or more applications associated with a browser-based user interface within a multi-developer computing platform employ one or more processors that receive a request to build one or more applications configured to run in a browser-based user interface on a client; determine whether the one or more applications are associated with a core library and one or more runtime libraries; and in response to determining that the one or more applications are associated with the core library and the one or more runtime libraries: determine one or more version numbers associated with the one or more runtime libraries; and in response to the determined one or more version numbers being within a predetermined range associated with the core library, dynamically link the one or more runtime libraries and the one or more applications.

First claim

What is claimed is:

1. A method for developing one or more applications associated with a browser-based user interface within a multi-developer computing platform, the method comprising:
receiving a request to build one or more applications configured to run in a browser-based user interface on a client;
determining whether the one or more applications are associated with a core library and one or more runtime libraries; and
in response to determining that the one or more applications are associated with the core library and the one or more runtime libraries:
determining one or more version numbers associated with the one or more runtime libraries;
in response to the determined one or more version numbers being within a predetermined range associated with the core library, dynamically linking the one or more runtime libraries and the one or more applications;

wherein the method is performed using one or more processors; and
wherein the core library comprises a library through which the one or more runtime libraries are called and includes an API layer for implementing and integrating common features across a multi-developer computing platform.

2. The method of claim 1 , and further comprising:
in response to the determined one or more version numbers being outside the predetermined range associated with the core library, statically linking the one or more runtime libraries and the one or more applications.

3. The method of claim 1 , and further comprising:
in response to the determined one or more version numbers being within the predetermined range associated with the core library, guaranteeing that the dynamically linked one or more runtime libraries are accessible at runtime by the one or more applications through the browser-based user interface.

4. The method of claim 1 wherein the core library is a NPM package.

5. The method of claim 1 wherein the core library allows at least one of the applications of the plurality of applications to interact with workspace runtime application interfaces (APIs) by importing the workspace runtime APIs from a versioned package as if they were another front-end library.

6. The method of claim 1 wherein the browser-based user interface is configured to run the one or more applications in a single-threaded mode.

7. A system for developing one or more applications associated with a browser-based user interface within a multi-developer computing platform, the system comprising:
one or more processors configured to:
receive a request to build one or more applications configured to run in a browser-based user interface on a client;
determine whether the one or more applications are associated with a core library and one or more runtime libraries; and
in response to determining that the one or more applications are associated with the core library and the one or more runtime libraries:
determine one or more version numbers associated with the one or more runtime libraries;
in response to the determined one or more version numbers being within a predetermined range associated with the core library, dynamically link the one or more runtime libraries and the one or more applications; and
wherein the core library comprises a library through which the one or more runtime libraries are called and includes an API layer for implementing and integrating common features across a multi-developer computing platform.

8. The system of claim 7 , wherein the one or more processors are configured to:
in response to the determined one or more version numbers being outside the predetermined range associated with the core library, statically link the one or more runtime libraries and the one or more applications.

9. The system of claim 7 wherein the one or more processors are configured to:
in response to the determined one or more version numbers being within the predetermined range associated with the core library, guarantee that the dynamically linked one or more runtime libraries are accessible at runtime by the one or more applications through the browser-based user interface.

10. The system of claim 7 wherein the core library is a NPM package.

11. The system of claim 7 wherein the core library allows at least one of the applications of the plurality of applications to interact with workspace runtime application interfaces (APIs) by importing the workspace runtime APIs from a versioned package as if they were another front-end library.

12. The system of claim 7 wherein the browser-based user interface is configured to run the one or more applications in a single-threaded mode.

13. A system for upgrading applications associated with a browser-based user interface within a multi-developer computing platform, the system comprising:
one or more clients including a browser-based user interface;
one or more processors of a computing platform configured to:
interface with a first core library and a second core library, each of the first core library and the second core library being associated with different versions of one or more runtime libraries and configured to provide applications with access to the different versions of the one or more runtime libraries through the browser-based user interface;
determine the versions of the one or more runtime libraries being accessed through a log file generated by the first core library and the second core library;
in response to determining that no versions of the one or more runtime libraries of the first core library is being accessed for a predetermined time period, terminate the first core library; and
wherein the core library comprises a library through which the one or more runtime libraries are called and incudes an API laver for implementing and integrating common features across a multi-developer computing platform.

14. The system of claim 13 wherein the first core library and the second core library are NPM packages.

15. The system of claim 13 , and further comprising:
in response to determining that no versions of the one or more runtime libraries of the first core library is being accessed for a predetermined time period, provide a third core library, each of the first core library, the second core library and the third core library being associated with different versions of the one or more runtime libraries.

16. The system of claim 13 wherein the browser-based user interface is further configured to run the applications in a single-threaded mode.

17. The system of claim 13 wherein the core library core library allows at least one of the applications of the plurality of applications to interact with workspace runtime application interfaces (APIs) by importing the workspace runtime APIs from a versioned package as if they were another front-end library.

Assignees

• Palantir Technologies Inc

Inventors

• Yu Stephanie
• Burgin Walker
• Ryan Alexander
• Danka Miklos

Classifications

• G06F9/451

  Execution arrangements for user interfaces · CPC title

• G06F8/40

  Transformation of program code · CPC title

• G06F8/54

  Link editing before load time · CPC title

• G06F9/44521 Primary

  Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading · CPC title

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title