CN116149882A - Method, device, equipment and storage medium for generating interface description file - Google Patents

Method, device, equipment and storage medium for generating interface description file Download PDF

Info

Publication number
CN116149882A
CN116149882A CN202310416904.1A CN202310416904A CN116149882A CN 116149882 A CN116149882 A CN 116149882A CN 202310416904 A CN202310416904 A CN 202310416904A CN 116149882 A CN116149882 A CN 116149882A
Authority
CN
China
Prior art keywords
information
branch
target branch
interface description
target
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202310416904.1A
Other languages
Chinese (zh)
Other versions
CN116149882B (en
Inventor
张轩铭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Easy Yikang Information Technology Co ltd
Original Assignee
Beijing Qingsongchou Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Qingsongchou Information Technology Co ltd filed Critical Beijing Qingsongchou Information Technology Co ltd
Priority to CN202310416904.1A priority Critical patent/CN116149882B/en
Publication of CN116149882A publication Critical patent/CN116149882A/en
Application granted granted Critical
Publication of CN116149882B publication Critical patent/CN116149882B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/544—Buffers; Shared memory; Pipes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/541—Client-server
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/544—Remote
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application provides a method, a device, equipment and a storage medium for generating an interface description file, wherein the method comprises the steps of receiving a trigger event request sent by a client when a remote call task is triggered, wherein the trigger event request comprises a push source code event request and a merging source code event request; acquiring information of a target branch based on a trigger event request; and generating an interface description file according to the information of the target branch and the change information of the original code item, and pushing the interface description file to the corresponding remote branch. The method can achieve the effect of automatically generating the corresponding interface description file according to the current network environment.

Description

Method, device, equipment and storage medium for generating interface description file
Technical Field
The present application relates to the field of remote invocation, and in particular, to a method, apparatus, device, and storage medium for generating an interface description file.
Background
Currently, interface description languages are commonly used for remote invocation of software, in which case the object components on different operating systems are typically invoked by remote client terminals, and may be written in different computer languages. The interface description language establishes a bridge for communication between two different operating systems. After the corresponding interface description file is written in the development work, each language tool class is generated through the tool package to call the interface description language file.
The method has great limitation, and when development environments of developers are different, the corresponding tool kit needs to be reinstalled to call the corresponding interface description file.
Therefore, how to automatically generate the corresponding interface description file according to the current network environment is a technical problem to be solved.
Disclosure of Invention
The embodiment of the application aims to provide a method for generating interface description files, and the effect of automatically generating corresponding interface description files according to the current network environment can be achieved through the technical scheme of the embodiment of the application.
In a first aspect, an embodiment of the present application provides a method for generating an interface description file, including, when triggering a remote invocation task, receiving a triggering event request sent by a client, where the triggering event request includes a push source code event request and a merge source code event request; acquiring information of a target branch based on a trigger event request; and generating an interface description file according to the information of the target branch and the change information of the original code item, and pushing the interface description file to the corresponding remote branch.
In the above embodiment, when a remote call task is performed, the obtained target branch information may be combined with the change information of the original code item to automatically generate the corresponding interface description file. The effect of automatically generating the corresponding interface description file according to the current network environment is achieved.
In some embodiments, based on the trigger event request, obtaining information for the target branch includes:
acquiring all branch information corresponding to an original code item;
determining whether a target branch exists locally;
when the local existence of the target branch is determined, acquiring information of the target branch in all branch information;
when it is determined that the target branch does not exist locally, the target branch is newly established and information of the target branch in all branch information is acquired.
In the above embodiment, the target branch information can be accurately acquired or constructed by acquiring all the branch information of the original code item.
In some embodiments, obtaining all branch information corresponding to the original code item includes:
determining whether an original code item exists in the cache directory;
when the original code items exist in the cache directory, acquiring all corresponding branch information;
when the original code item does not exist in the cache directory, the original code item in the client is copied and stored in the cache directory, and all corresponding branch information is acquired.
In the above embodiment, all branch information can be accurately obtained by caching the original code item in the directory.
In some embodiments, based on the trigger event request, obtaining information for the target branch includes:
determining whether an interface description code item exists in the cache directory;
when the fact that the interface description code items exist in the cache directory is determined, acquiring corresponding second all branch information;
and when the fact that the interface description code item does not exist in the cache directory is determined, copying the interface description code item in the client, storing the interface description code item in the cache directory, and acquiring corresponding second all branch information.
In the above embodiment, the second all branch information may be accurately obtained by caching the interface description code item in the directory.
In some embodiments, when it is determined that the interface description code item does not exist in the cache directory, copying the interface description code item in the client and storing the interface description code item in the cache directory, and acquiring the corresponding second all branch information, further includes:
determining whether a second target branch exists locally;
when the second target branch is determined to exist locally, the information of the second target branch in the second all branch information is taken as the information of the target branch;
when it is determined that the second target branch does not exist locally, the second target branch is newly created and information of the second target branch in the second total branch information is taken as information of the target branch or information of a third target branch of the remote service is taken as information of the target branch.
In the above embodiment, the information of the target branch can be accurately acquired by acquiring or establishing the local second target branch or acquiring the third branch of the remote service.
In some embodiments, after creating the second target branch and taking information of the second target branch in the second total branch information as information of the target branch or taking information of a third target branch of the remote service as information of the target branch when it is determined that the second target branch does not exist locally, further comprising:
when it is determined that the second target branch does not exist locally and the third target branch does not exist at the remote service;
a fourth target branch is created based on the current version of the main branch, and information of the fourth target branch is taken as information of the target branch.
In the above embodiment, the fourth target branch may be created through the main branch, so that information of the target branch may be accurately obtained.
In some embodiments, generating an interface description file and pushing the interface description file to a corresponding remote branch according to information of the target branch and change information of an original code item, including:
sorting the files corresponding to the change information of the original code item according to the submitting time to obtain sorted change information files, wherein the change information files comprise newly added files, modified files and deleted files;
And merging the sequenced change information file and the information of the target branch into an interface description file and pushing the interface description file to the corresponding remote branch.
In the above embodiment, the interface description file can be accurately constructed by combining the change information and the target branch information.
In some embodiments, when triggering the remote call task, after receiving the trigger event request sent by the client, the method further includes:
based on the trigger event request, distinguishing event types triggered by the request, wherein the event types comprise push source code events and merge source code events.
In the above embodiment, the event types can be accurately distinguished according to the trigger event request.
In some embodiments, after merging the ordered change information file and the information of the target branch into an interface description file and pushing the interface description file to the corresponding remote branch, the method further includes:
when the event type is determined to be a merging source code event, determining whether to delete the corresponding source branch in the interface description code item according to whether the instruction parameter for deleting the source branch exists in the merging source code event.
In the above embodiment, whether to delete the corresponding source branch in the interface description code item or not may be determined according to the instruction, and the memory is released.
In some embodiments, the method further comprises:
and when program errors occur and the remote call task is interrupted, restoring all changed information in the interface description code item to an initial state.
In the embodiment of the present application, all the changed information in the interface description code item can be restored to the initial state, so that subsequent processing conflicts caused by inconsistent item files and remote in the cache are avoided.
In a second aspect, an embodiment of the present application provides an apparatus for generating an interface description file, including:
the receiving module is used for receiving a trigger event request sent by the client when the remote call task is triggered, wherein the trigger event request comprises a pushing source code event request and a merging source code event request;
the acquisition module is used for acquiring information of the target branch based on the trigger event request;
and the generation module is used for generating an interface description file according to the information of the target branch and the change information of the original code item and pushing the interface description file to the corresponding remote branch.
Optionally, the acquiring module is specifically configured to:
acquiring all branch information corresponding to an original code item;
determining whether a target branch exists locally;
When the local existence of the target branch is determined, acquiring information of the target branch in all branch information;
when it is determined that the target branch does not exist locally, the target branch is newly established and information of the target branch in all branch information is acquired.
Optionally, the acquiring module is specifically configured to:
determining whether an original code item exists in the cache directory;
when the original code items exist in the cache directory, acquiring all corresponding branch information;
when the original code item does not exist in the cache directory, the original code item in the client is copied and stored in the cache directory, and all corresponding branch information is acquired.
Optionally, the acquiring module is specifically configured to:
determining whether an interface description code item exists in the cache directory;
when the fact that the interface description code items exist in the cache directory is determined, acquiring corresponding second all branch information;
and when the fact that the interface description code item does not exist in the cache directory is determined, copying the interface description code item in the client, storing the interface description code item in the cache directory, and acquiring corresponding second all branch information.
Optionally, the apparatus further includes:
the determining module is used for determining whether a second target branch exists locally or not after the obtaining module copies the interface description code item in the client and stores the interface description code item in the cache directory and obtains the corresponding second whole branch information when determining that the interface description code item does not exist in the cache directory;
When the second target branch is determined to exist locally, the information of the second target branch in the second all branch information is taken as the information of the target branch;
when it is determined that the second target branch does not exist locally, the second target branch is newly created and information of the second target branch in the second total branch information is taken as information of the target branch or information of a third target branch of the remote service is taken as information of the target branch.
Optionally, the apparatus further includes:
a building module, configured to, when it is determined that the second target branch does not exist locally and the third target branch does not exist remotely, after determining that the second target branch does not exist locally and the information of the second target branch is taken as the information of the target branch or the information of the third target branch of the remote service in the second total branch information;
a fourth target branch is created based on the current version of the main branch, and information of the fourth target branch is taken as information of the target branch.
Optionally, the generating module is specifically configured to:
sorting the files corresponding to the change information of the original code item according to the submitting time to obtain sorted change information files, wherein the change information files comprise newly added files, modified files and deleted files;
And merging the sequenced change information file and the information of the target branch into an interface description file and pushing the interface description file to the corresponding remote branch.
Optionally, the apparatus further includes:
and the judging module is used for distinguishing event types triggered by the request based on the trigger event request after the receiving module receives the trigger event request sent by the client when triggering the remote call task, wherein the event types comprise pushing source code events and merging source code events.
Optionally, the apparatus further includes:
and the deleting module is used for determining whether to delete the corresponding source branch in the interface description code item according to whether the instruction parameter for deleting the source branch exists in the merging source code event when the event type is determined to be the merging source code event after the generation module merges the sequenced change information file and the information of the target branch into the interface description file and pushes the interface description file to the corresponding remote branch.
Optionally, the apparatus further includes:
the restoring module is specifically configured to restore all the changed information in the interface description code item to an initial state when the remote call task is interrupted due to a program error.
In a third aspect, embodiments of the present application provide an electronic device comprising a processor and a memory storing computer readable instructions that, when executed by the processor, perform the steps of the method as provided in the first aspect above.
In a fourth aspect, embodiments of the present application provide a readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the method as provided in the first aspect above.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the embodiments of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a method for generating an interface description file according to an embodiment of the present application;
FIG. 2 is a flowchart of an implementation method for generating an interface description file according to an embodiment of the present application;
FIG. 3 is a schematic block diagram of an apparatus for generating an interface description file according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an apparatus for generating an interface description file according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. The components of the embodiments of the present application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, as provided in the accompanying drawings, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, are intended to be within the scope of the present application.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only to distinguish the description, and are not to be construed as indicating or implying relative importance.
Some of the terms referred to in the embodiments of the present application will be described first to facilitate understanding by those skilled in the art.
Terminal equipment: the mobile terminal, stationary terminal or portable terminal may be, for example, a mobile handset, a site, a unit, a device, a multimedia computer, a multimedia tablet, an internet node, a communicator, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a personal communications system device, a personal navigation device, a personal digital assistant, an audio/video player, a digital camera/camcorder, a positioning device, a television receiver, a radio broadcast receiver, an electronic book device, a game device, or any combination thereof, including the accessories and peripherals of these devices, or any combination thereof. It is also contemplated that the terminal device can support any type of interface (e.g., wearable device) for the user, etc.
And (3) a server: the cloud server can be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and can also be a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, basic cloud computing services such as big data and artificial intelligent platforms and the like.
gRPC: "Google Remote Procedure Call, google remote procedure call", GRPC can automatically generate a function library directly through a client and a server. The user can select the appropriate mode according to his own needs. When the client calls the server, the client sends a request to the server and gets a response, and some data is sent with the response.
Protocol Buffers: a data description language, similar to XML, can serialize structured data, and can be used in data storage, communication protocols, and the like.
Interface description language: (Interface description language, abbreviated IDL), is a computer language used to describe software component interfaces. IDL describes interfaces in a programming language independent manner, so that objects running on different platforms and programs written in different languages can communicate with each other; for example, one component is written in Golang and the other component is written in Java.
PB: the content is actually plain text, and can be opened by a text editor, such as notepad, notpad++, etc.
WebHooks: one api concept, one of the usage paradigms of micro-service apis, is also called reverse api, i.e., the front end does not actively send requests and is pushed by the back end entirely.
The method and the device are applied to remote call scenes, and specific scenes are original codes uniformly developed through a server and corresponding interface description files are automatically generated according to changes of the original codes.
Currently, interface description languages are commonly used for remote invocation of software, in which case the object components on different operating systems are typically invoked by remote client terminals, and may be written in different computer languages. The interface description language establishes a bridge for communication between two different operating systems. After the corresponding interface description file is written in the development work, each language tool class is generated through the tool package to call the interface description language file. The method has great limitation, and when development environments of developers are different, the corresponding tool kit needs to be reinstalled to call the corresponding interface description file.
For example, after writing the corresponding IDL file in the development work, each language tool class needs to be generated by a tool package, for example, golang (a static strong type, compiled language) needs a developer to install two tools, protobuf (a data description language tool) and protoc-gen-go (a data description language tool), on the client to generate protoc-gen-go of the corresponding proto (original code item) file for calling. Therefore, development using gRPC requires additional configuration of PB file generation environment, and the installation cost of the required tool kit is high due to factors such as network environment; different developer development environments are inconsistent in default installed tool versions, so that generated PB file versions are inconsistent, and team cooperation efficiency is affected; after the proto file is updated, the corresponding PB file is forgotten to be updated, so that the problem is difficult to find, and the time is delayed.
The method comprises the steps that when a remote call task is triggered, a trigger event request sent by a client is received, wherein the trigger event request comprises a push source code event request and a merging source code event request; acquiring information of a target branch based on a trigger event request; and generating an interface description file according to the information of the target branch and the change information of the original code item, and pushing the interface description file to the corresponding remote branch. When a remote call task is carried out, a corresponding interface description file can be automatically generated by combining the acquired target branch information with the change information of the original code item. The effect of automatically generating the corresponding interface description file according to the current network environment is achieved.
In the embodiment of the present application, the execution body may generate the interface description file device in the interface description file system, and in practical application, the interface description file device may be electronic devices such as a terminal device and a server, which is not limited herein.
The method for generating the interface description file according to the embodiment of the present application is described in detail below with reference to fig. 1.
Referring to fig. 1, fig. 1 is a flowchart of a method for generating an interface description file according to an embodiment of the present application, where the method for generating an interface description file shown in fig. 1 includes:
step 110: and when the remote call task is triggered, receiving a trigger event request sent by the client.
Wherein the trigger event request includes a push source code event request and a merge source code event request. The remote call task can be a method of calling an application program from a server through a client, the application can use gRPC to realize the call of the remote task, can be extended to all used interface description file communication protocols, can directly automatically generate a function library through the client and a server, and sends a request to the server and obtains a response by the client when the client calls the server. The gRPC may use protocol-buffers as an interface description language for describing the structure of service interfaces and payload messages.
In some embodiments of the present application, after receiving a trigger event request sent by a client when triggering a remote call task, the method shown in fig. 1 further includes: based on the trigger event request, distinguishing event types triggered by the request, wherein the event types comprise push source code events and merge source code events.
In the process, the event types can be accurately distinguished according to the trigger event request.
The source code pushing event may be an event of pushing the native code or the source code of the original branch to the target far-end branch, and the source code merging event may be an event of putting the native code or the source code into a branch and merging the native code or the source code into the target branch after passing the branch test.
Step 120: based on the trigger event request, information of the target branch is acquired.
Wherein the target branches further include a locally stored second target branch, a third branch of a remote service, or a fourth branch created by replicating the primary branch, etc. The information of the target branch also includes information of the second target branch, information of the third target branch, information of the fourth target branch, or the like. The information of the target branch may be program code of a remotely invoked application.
In one embodiment, triggering of the trigger event may be performed by a WebHook function deploying a code repository (e.g., a GitLab (a code repository) or other code repository), into the application server (Web server).
In some embodiments of the present application, based on a trigger event request, obtaining information of a target branch includes: acquiring all branch information corresponding to an original code item; determining whether a target branch exists locally; when the local existence of the target branch is determined, acquiring information of the target branch in all branch information; when it is determined that the target branch does not exist locally, the target branch is newly established and information of the target branch in all branch information is acquired.
In the process, the target branch information can be accurately acquired or constructed by acquiring all the branch information of the original code item.
Wherein the original code item (Proto) comprises program development original code of a remote caller, and has a separate code repository for maintaining an original code item readable file. All the branch information comprises at least one of main branch information, original branch information, local branch information and target branch information, and the information of the target branch can be obtained by copying the main branch information, the original branch information and the local branch information.
In one embodiment, after creating a target branch and acquiring information of the target branch in all branch information when it is determined that the target branch does not exist locally, the method shown in fig. 1 further includes:
and switching the current development environment to the newly built target branch, and updating the newly built target branch to the target branch of the latest version.
In some embodiments of the present application, obtaining all branch information corresponding to an original code item includes: determining whether an original code item exists in the cache directory; when the original code items exist in the cache directory, acquiring all corresponding branch information; when the original code item does not exist in the cache directory, the original code item in the client is copied and stored in the cache directory, and all corresponding branch information is acquired.
In the process, all branch information can be accurately acquired by caching the original code items in the directory.
The cache directory is used for storing original code items, interface description code items (PB) and corresponding program development codes, wherein the interface description code items are provided with independent code warehouses and are used for maintaining interface description code item readable files.
In some embodiments of the present application, based on a trigger event request, obtaining information of a target branch includes: determining whether an interface description code item exists in the cache directory; when the fact that the interface description code items exist in the cache directory is determined, acquiring corresponding second all branch information; and when the fact that the interface description code item does not exist in the cache directory is determined, copying the interface description code item in the client, storing the interface description code item in the cache directory, and acquiring corresponding second all branch information.
In the above process, the second whole branch information can be accurately obtained by caching the interface description code item in the directory.
Wherein the second total branch information includes at least one of main branch information, original branch information, information of the local branch, and information of the second target branch.
In some embodiments of the present application, after copying the interface description code item in the client and storing it in the cache directory and acquiring the corresponding second total branch information when it is determined that the interface description code item does not exist in the cache directory, the method shown in fig. 1 further includes: determining whether a second target branch exists locally; when the second target branch is determined to exist locally, the information of the second target branch in the second all branch information is taken as the information of the target branch; when it is determined that the second target branch does not exist locally, the second target branch is newly created and information of the second target branch in the second total branch information is taken as information of the target branch or information of a third target branch of the remote service is taken as information of the target branch.
In the process, the information of the target branch can be accurately acquired by acquiring or establishing the local second target branch or acquiring the third branch of the remote service.
In some embodiments of the present application, after creating the second target branch and taking information of the second target branch in the second total branch information as information of the target branch or taking information of the third target branch of the remote service as information of the target branch when it is determined that the second target branch does not exist locally, the method shown in fig. 1 further includes: when it is determined that the second target branch does not exist locally and the third target branch does not exist at the remote service; a fourth target branch is created based on the current version of the main branch, and information of the fourth target branch is taken as information of the target branch.
In the above process, the fourth target branch can be created through the main branch, so that the information of the target branch can be accurately acquired.
Wherein creating the fourth target branch based on the current version of the main branch includes copying the current latest version of the main branch information into the fourth target branch.
In one embodiment, after creating the fourth target branch based on the current version of the main branch and taking the information of the fourth target branch as the information of the target branch, the method shown in fig. 1 further includes:
The main branch is switched to the current development environment.
Step 130: and generating an interface description file according to the information of the target branch and the change information of the original code item, and pushing the interface description file to the corresponding remote branch.
The change information includes file information newly added, modified and deleted according to Commit (operation instruction) in the original code item, for example, a list of some newly added, modified and deleted files, program code and the like. The remote branch may be a remote server.
In one embodiment, the remote server implements a description of the interface based on the interface description file, enabling communication between the remote server and the client, which can directly access the method on the application in the server.
In some embodiments of the present application, generating an interface description file according to information of a target branch and change information of an original code item and pushing the interface description file to a corresponding remote branch includes: sorting the files corresponding to the change information of the original code item according to the submitting time to obtain sorted change information files, wherein the change information files comprise newly added files, modified files and deleted files; and merging the sequenced change information file and the information of the target branch into an interface description file and pushing the interface description file to the corresponding remote branch.
In the process, the interface description file can be accurately constructed by combining the change information and the target branch information.
The new file comprises a new information file, the modified file comprises a file of modified information, the deleted file comprises a file of deleted information, and the new addition, the modification and the deletion can be realized aiming at code information.
In some embodiments of the present application, after merging the ordered change information file and the information of the target branch into an interface description file and pushing the interface description file to the corresponding remote branch, the method shown in fig. 1 further includes: when the event type is determined to be a merging source code event, determining whether to delete the corresponding source branch in the interface description code item according to whether the instruction parameter for deleting the source branch exists in the merging source code event.
In the above process, the method can determine whether to delete the corresponding source branch in the interface description code item according to the instruction, and release the memory.
In some embodiments of the present application, the method shown in fig. 1 further includes: and when program errors occur and the remote call task is interrupted, restoring all changed information in the interface description code item to an initial state.
In the process, the method and the device can restore all changed information in the interface description code item to an initial state, and avoid subsequent processing conflict caused by inconsistent item files and remote in the cache.
Wherein the information of all the changes includes the change information of the original code item.
In addition, through the steps, the corresponding interface description file can be automatically generated in a unified environment through each information change in the original code project, and the interface description file is pushed to a code warehouse of a remote server for each client to be referenced.
In the process shown in fig. 1, the application receives a trigger event request sent by a client when triggering a remote call task, where the trigger event request includes a push source code event request and a merge source code event request; acquiring information of a target branch based on a trigger event request; and generating an interface description file according to the information of the target branch and the change information of the original code item, and pushing the interface description file to the corresponding remote branch. When a remote call task is carried out, a corresponding interface description file can be automatically generated by combining the acquired target branch information with the change information of the original code item. The effect of automatically generating the corresponding interface description file according to the current network environment is achieved.
The following describes in detail an implementation method for generating an interface description file according to an embodiment of the present application with reference to fig. 2.
Referring to fig. 2, fig. 2 is a flowchart of an implementation method for generating an interface description file according to an embodiment of the present application, where the implementation method for generating an interface description file shown in fig. 2 includes:
step 201: triggering a remote call task.
Specific: and when the remote call task is triggered, receiving a trigger event request sent by the client. And proceeds to steps 202 and 218.
Step 202: branch B1 of the push source code event is taken.
Specific: information of target branches B1 and B1 is acquired. Where B1 may represent the target branch, the second target branch, the third target branch, or the fourth target branch in fig. 1.
Step 203: whether the cache directory is in proco.
Specific: if the original code item is in the cache directory, the process proceeds to step 205, and the process continues to step 204.
Step 204: proto in Clone cache directory.
Specific: clone original code items and cache directories.
Step 205: all the branch information is acquired.
Specific: and acquiring all branch information corresponding to the original code item.
Step 206: whether branch B1 exists locally.
Specific: it is determined whether there is a target branch locally, and the process proceeds to step 207, otherwise, to step 208.
Step 207: the local branch is switched to B1 and updated to up-to-date.
Specific: the local target branch is taken as B1 and updated to the latest development environment, and the process proceeds to step 209.
Step 208: the local branch B1 is created on the basis of the remote service branch.
Specific: and obtaining a remote branch or copying the remote branch to obtain B1.
Step 209: whether the cached directory is in PB.
Specific: it is determined whether an interface description code item exists in the cache, and the process proceeds to step 211, otherwise, to step 210.
Step 210: the Clone caches the PB in the directory.
Specific: the copy interface describes the code entry and cache directory.
Step 211: all the branch information is acquired.
Specific: and acquiring all branch information corresponding to the interface description code item.
Step 212: whether branch B1 exists for PB item.
Specific: if B1 exists in the interface description code item, the process proceeds to step 216, otherwise, the process proceeds to step 213.
Step 213: whether B1 is present locally.
Specific: if there is a target branch B1 locally, there is an entry to step 215, otherwise, there is an entry to step 214.
Step 214: the local branch B1 is created on the basis of the remote service branch.
Specific: acquire remote service branch or copy remote service branch, get B1, and go to step 217.
Step 215: the local branch is switched to B1 and updated to up-to-date.
Specific: the local branch is taken as the target branch B1 and is switched to the latest development environment. And proceeds to step 217.
Step 216: b1 is created on the basis of the main branch.
Specific: the primary branch is replicated as target branch B1.
Step 217: and acquiring a change information list of the push source code event.
Specific: and acquiring a change information file of the new addition, modification and deletion of the push source code event. And proceeds to step 219.
Step 218: and acquiring a change information list of the merging source code event.
Specific: and acquiring a change information file combining the new addition, modification and deletion of the source code event.
Step 219: and generating PB according to the newly added file and modifying PB according to the modified file.
Specific: generating PB from the newly added file and modifying to obtain modified PB.
Step 220: and deleting the corresponding deleted file in the PB.
Specific: and deleting the files to be deleted in the modified PB to obtain the interface description file.
Step 221: pushing the remote branches.
Specific: the interface description file is pushed to the remote branch.
In addition, the specific method and steps shown in fig. 2 may refer to the method shown in fig. 1, and will not be described in detail herein.
The method of generating the interface description file is described above through fig. 1 to 2, and the apparatus for generating the interface description file is described below with reference to fig. 3 to 4.
Referring to fig. 3, a schematic block diagram of an apparatus 300 for generating an interface description file according to an embodiment of the present application is provided, where the apparatus 300 may be a module, a program segment, or a code on an electronic device. The apparatus 300 corresponds to the embodiment of the method of fig. 1 described above, and is capable of performing the steps involved in the embodiment of the method of fig. 1. Specific functions of the apparatus 300 will be described below, and detailed descriptions thereof will be omitted herein as appropriate to avoid redundancy.
Optionally, the apparatus 300 includes:
a receiving module 310, configured to receive a trigger event request sent by a client when triggering a remote invocation task, where the trigger event request includes a push source code event request and a merge source code event request;
an obtaining module 320, configured to obtain information of the target branch based on the trigger event request;
The generating module 330 is configured to generate an interface description file according to the information of the target branch and the change information of the original code item, and push the interface description file to the corresponding remote branch.
Optionally, the acquiring module is specifically configured to:
acquiring all branch information corresponding to an original code item; determining whether a target branch exists locally; when the local existence of the target branch is determined, acquiring information of the target branch in all branch information; when it is determined that the target branch does not exist locally, the target branch is newly established and information of the target branch in all branch information is acquired.
Optionally, the acquiring module is specifically configured to:
determining whether an original code item exists in the cache directory; when the original code items exist in the cache directory, acquiring all corresponding branch information; when the original code item does not exist in the cache directory, the original code item in the client is copied and stored in the cache directory, and all corresponding branch information is acquired.
Optionally, the acquiring module is specifically configured to:
determining whether an interface description code item exists in the cache directory; when the fact that the interface description code items exist in the cache directory is determined, acquiring corresponding second all branch information; and when the fact that the interface description code item does not exist in the cache directory is determined, copying the interface description code item in the client, storing the interface description code item in the cache directory, and acquiring corresponding second all branch information.
Optionally, the apparatus further includes:
the determining module is used for determining whether a second target branch exists locally or not after the obtaining module copies the interface description code item in the client and stores the interface description code item in the cache directory and obtains the corresponding second whole branch information when determining that the interface description code item does not exist in the cache directory; when the second target branch is determined to exist locally, the information of the second target branch in the second all branch information is taken as the information of the target branch; when it is determined that the second target branch does not exist locally, the second target branch is newly created and information of the second target branch in the second total branch information is taken as information of the target branch or information of a third target branch of the remote service is taken as information of the target branch.
Optionally, the apparatus further includes:
a building module, configured to, when it is determined that the second target branch does not exist locally and the third target branch does not exist remotely, after determining that the second target branch does not exist locally and the information of the second target branch is taken as the information of the target branch or the information of the third target branch of the remote service in the second total branch information; a fourth target branch is created based on the current version of the main branch, and information of the fourth target branch is taken as information of the target branch.
Optionally, the generating module is specifically configured to:
sorting the files corresponding to the change information of the original code item according to the submitting time to obtain sorted change information files, wherein the change information files comprise newly added files, modified files and deleted files; and merging the sequenced change information file and the information of the target branch into an interface description file and pushing the interface description file to the corresponding remote branch.
Optionally, the apparatus further includes:
and the judging module is used for distinguishing event types triggered by the request based on the trigger event request after the receiving module receives the trigger event request sent by the client when triggering the remote call task, wherein the event types comprise pushing source code events and merging source code events.
Optionally, the apparatus further includes:
and the deleting module is used for determining whether to delete the corresponding source branch in the interface description code item according to whether the instruction parameter for deleting the source branch exists in the merging source code event when the event type is determined to be the merging source code event after the generation module merges the sequenced change information file and the information of the target branch into the interface description file and pushes the interface description file to the corresponding remote branch.
Optionally, the apparatus further includes:
the restoring module is specifically configured to restore all the changed information in the interface description code item to an initial state when the remote call task is interrupted due to a program error.
Referring to fig. 4, a schematic structural diagram of an apparatus for generating an interface description file according to an embodiment of the present application may include a memory 410 and a processor 420. Optionally, the apparatus may further include: a communication interface 430 and a communication bus 440. The apparatus corresponds to the embodiment of the method of fig. 1 described above, and is capable of performing the steps involved in the embodiment of the method of fig. 1, and specific functions of the apparatus may be found in the following description.
In particular, the memory 410 is used to store computer readable instructions.
The processor 420, which processes the readable instructions stored in the memory, is capable of performing the various steps in the method of fig. 1.
Communication interface 430 is used for signaling or data communication with other node devices. For example: for communication with a server or terminal, or with other device nodes, the embodiments of the application are not limited in this regard.
A communication bus 440 for enabling direct connection communication of the above-described components.
The communication interface 430 of the device in the embodiment of the present application is used for performing signaling or data communication with other node devices. The memory 410 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. Memory 410 may also optionally be at least one storage device located remotely from the aforementioned processor. The memory 410 has stored therein computer readable instructions which, when executed by the processor 420, perform the method process described above in fig. 1. Processor 420 may be used on apparatus 300 and to perform the functions herein. By way of example, the processor 420 described above may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, and the embodiments are not limited in this regard.
Embodiments of the present application also provide a readable storage medium, which when executed by a processor, performs a method process performed by an electronic device in the method embodiment shown in fig. 1.
It will be clear to those skilled in the art that, for convenience and brevity of description, reference may be made to the corresponding procedure in the foregoing method for the specific working procedure of the apparatus described above, and this will not be repeated here.
In summary, the embodiments of the present application provide a method, apparatus, device, and storage medium for generating an interface description file, where the method includes receiving a trigger event request sent by a client when a remote call task is triggered, where the trigger event request includes a push source code event request and a merge source code event request; acquiring information of a target branch based on a trigger event request; and generating an interface description file according to the information of the target branch and the change information of the original code item, and pushing the interface description file to the corresponding remote branch. The method can achieve the effect of automatically generating the corresponding interface description file according to the current network environment.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners as well. The apparatus embodiments described above are merely illustrative, for example, flow diagrams and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application, and various modifications and variations may be suggested to one skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application. It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Claims (13)

1. A method of generating an interface description file, comprising:
when a remote call task is triggered, receiving a trigger event request sent by a client, wherein the trigger event request comprises a push source code event request and a merging source code event request;
acquiring information of a target branch based on the trigger event request;
and generating an interface description file according to the information of the target branch and the change information of the original code item, and pushing the interface description file to the corresponding remote branch.
2. The method of claim 1, wherein the obtaining information of the target branch based on the trigger event request comprises:
acquiring all branch information corresponding to the original code item;
determining whether the target branch exists locally;
when the target branch is determined to exist locally, acquiring information of the target branch in the all branch information;
and when the target branch is determined to be not present locally, creating the target branch and acquiring information of the target branch in the all branch information.
3. The method according to claim 2, wherein the obtaining all branch information corresponding to the original code item includes:
Determining whether the original code item exists in a cache directory;
when the original code items exist in the cache directory, acquiring all corresponding branch information;
and when the original code item does not exist in the cache directory, copying the original code item in the client, storing the original code item in the cache directory, and acquiring the corresponding all branch information.
4. A method according to any of claims 1-3, wherein said obtaining information of a target branch based on said trigger event request comprises:
determining whether an interface description code item exists in the cache directory;
when the fact that the interface description code item exists in the cache directory is determined, acquiring corresponding second all branch information;
and when the fact that the interface description code item does not exist in the cache directory is determined, copying the interface description code item in the client, storing the interface description code item in the cache directory, and acquiring the corresponding second all branch information.
5. The method of claim 4, wherein upon said determining that said interface description code item does not exist in said cache directory, copying said interface description code item in said client and storing it in said cache directory, and obtaining said corresponding second total branching information, said method further comprises:
Determining whether a second target branch exists locally;
when the second target branch is determined to exist locally, the information of the second target branch in the second total branch information is taken as the information of the target branch;
and when the second target branch is determined to be not locally existed, creating the second target branch, and taking the information of the second target branch in the second total branch information as the information of the target branch or taking the information of a third target branch of remote service as the information of the target branch.
6. The method of claim 5, wherein after said creating said second target branch and taking information of said second target branch of said second total branch information as information of said target branch or information of a third target branch of a remote service as information of said target branch when said determining said absence of said second target branch locally, said method further comprises:
when it is determined that the second target branch is not present locally and the third target branch is not present by the remote service;
and creating a fourth target branch based on the main branch of the current version, and taking the information of the fourth target branch as the information of the target branch.
7. A method according to any one of claims 1-3, wherein generating an interface description file and pushing the interface description file to a corresponding remote branch based on the information of the target branch and the change information of the original code item comprises:
sorting the files corresponding to the change information of the original code item according to the submitting time to obtain sorted change information files, wherein the change information files comprise newly added files, modified files and deleted files;
and merging the sequenced change information file and the information of the target branch into the interface description file and pushing the interface description file to the remote branch.
8. The method of claim 7, wherein upon receiving a trigger event request sent by a client when triggering a remote invocation task, the method further comprises:
and distinguishing event types triggered by the request based on the trigger event request, wherein the event types comprise push source code events and merging source code events.
9. The method of claim 8, wherein after said merging the ordered change information file and the information of the target branch into the interface description file and pushing the interface description file to the corresponding remote branch, the method further comprises:
And when the event type is determined to be the merging source code event, determining whether to delete the corresponding source branch in the interface description code item according to whether the instruction parameter for deleting the source branch exists in the merging source code event.
10. A method according to any one of claims 1-3, wherein the method further comprises:
and when program errors occur to cause the remote call task to interrupt, restoring all changed information in the interface description code item to an initial state.
11. An apparatus for generating an interface description file, comprising:
the receiving module is used for receiving a trigger event request sent by the client when triggering the remote call task, wherein the trigger event request comprises a push source code event request and a combined source code event request;
the acquisition module is used for acquiring information of a target branch based on the trigger event request;
and the generation module is used for generating an interface description file according to the information of the target branch and the change information of the original code item and pushing the interface description file to the corresponding remote branch.
12. An electronic device, comprising:
A memory and a processor, the memory storing computer readable instructions that, when executed by the processor, perform the steps in the method of any of claims 1-10.
13. A computer-readable storage medium, comprising:
computer program which, when run on a computer, causes the computer to perform the method according to any one of claims 1-10.
CN202310416904.1A 2023-04-19 2023-04-19 Method, device, equipment and storage medium for generating interface description file Active CN116149882B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310416904.1A CN116149882B (en) 2023-04-19 2023-04-19 Method, device, equipment and storage medium for generating interface description file

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310416904.1A CN116149882B (en) 2023-04-19 2023-04-19 Method, device, equipment and storage medium for generating interface description file

Publications (2)

Publication Number Publication Date
CN116149882A true CN116149882A (en) 2023-05-23
CN116149882B CN116149882B (en) 2023-08-08

Family

ID=86358538

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310416904.1A Active CN116149882B (en) 2023-04-19 2023-04-19 Method, device, equipment and storage medium for generating interface description file

Country Status (1)

Country Link
CN (1) CN116149882B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110308930A (en) * 2019-06-18 2019-10-08 广州华多网络科技有限公司 Interface document generation method, device, computer equipment and storage medium
US20190325074A1 (en) * 2018-04-18 2019-10-24 International Business Machines Corporation Application programing interface document generator
CN113190448A (en) * 2021-05-06 2021-07-30 网易（杭州）网络有限公司 Test code updating method and device, electronic equipment and storage medium
CN114168190A (en) * 2020-09-11 2022-03-11 腾讯科技（深圳）有限公司 Interface document generation method and device, computer equipment and storage medium
CN114301970A (en) * 2021-12-21 2022-04-08 北京达佳互联信息技术有限公司 Service calling method and device, electronic equipment and storage medium
CN114443129A (en) * 2021-12-30 2022-05-06 广东南方新媒体科技有限公司 Project document automatic generation method, device and storage medium
CN115113854A (en) * 2021-03-23 2022-09-27 腾讯科技（深圳）有限公司 Interface document generation method, device, equipment and computer readable storage medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190325074A1 (en) * 2018-04-18 2019-10-24 International Business Machines Corporation Application programing interface document generator
CN110308930A (en) * 2019-06-18 2019-10-08 广州华多网络科技有限公司 Interface document generation method, device, computer equipment and storage medium
CN114168190A (en) * 2020-09-11 2022-03-11 腾讯科技（深圳）有限公司 Interface document generation method and device, computer equipment and storage medium
CN115113854A (en) * 2021-03-23 2022-09-27 腾讯科技（深圳）有限公司 Interface document generation method, device, equipment and computer readable storage medium
CN113190448A (en) * 2021-05-06 2021-07-30 网易（杭州）网络有限公司 Test code updating method and device, electronic equipment and storage medium
CN114301970A (en) * 2021-12-21 2022-04-08 北京达佳互联信息技术有限公司 Service calling method and device, electronic equipment and storage medium
CN114443129A (en) * 2021-12-30 2022-05-06 广东南方新媒体科技有限公司 Project document automatic generation method, device and storage medium

Also Published As

Publication number Publication date
CN116149882B (en) 2023-08-08

Similar Documents

Publication Publication Date Title
KR101076851B1 (en) A method for managing multiple file states for replicated files
US6873995B2 (en) Method, system, and program product for transaction management in a distributed content management application
US8433948B2 (en) Method and apparatus for realizing application high availability
US7774364B2 (en) Uniform name space referrals with location independence
AU2006200226B2 (en) File system represented inside a database
US20100030818A1 (en) System and method for applying once a transaction delivered in a message published asynchronously in a distributed database
US10901643B2 (en) Using log objects in object storage for durability of file objects in volatile memory
CN108563440B (en) Automatic adding method and device of list controller codes and readable storage medium
US11010401B2 (en) Efficient snapshot generation of data tables
KR20090031669A (en) Techniques to perform gradual upgrades
JP2003308210A (en) Method of replicating source file across networked resources and recording medium
CN111240892B (en) Data backup method and device
US7774792B2 (en) Automatic create, update and delete event publishing
CN113419766B (en) Method, device, equipment and storage medium for intelligently updating program logic
US12061901B2 (en) Documentation enforcement during compilation
US10606805B2 (en) Object-level image query and retrieval
US20050114644A1 (en) Deterministic system and method for implementing software distributed between a desktop and a remote device
US9411618B2 (en) Metadata-based class loading using a content repository
CN105593839A (en) Distributed disaster recovery file sync server system
CN114996337A (en) Multi-cluster database management system and method
US20060117320A1 (en) Sharing dynamically changing resources in software systems
CN115964061A (en) Plug-in updating method and device, electronic equipment and computer readable storage medium
US10558450B2 (en) Mechanism for customizing multiple computing devices
CN116149882B (en) Method, device, equipment and storage medium for generating interface description file
Lüer et al. The evolution of software evolvability

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
CP01 Change in the name or title of a patent holder

Address after: Room 716, floor 7, building 2, No. 28 Andingmen East Street, Dongcheng District, Beijing 100010

Patentee after: Beijing Easy Yikang Information Technology Co.,Ltd.

Address before: Room 716, floor 7, building 2, No. 28 Andingmen East Street, Dongcheng District, Beijing 100010

Patentee before: BEIJING QINGSONGCHOU INFORMATION TECHNOLOGY Co.,Ltd.

CP01 Change in the name or title of a patent holder