CN111796802B - Function package generation method and device and electronic equipment - Google Patents
Function package generation method and device and electronic equipment Download PDFInfo
- Publication number
- CN111796802B CN111796802B CN202010617829.1A CN202010617829A CN111796802B CN 111796802 B CN111796802 B CN 111796802B CN 202010617829 A CN202010617829 A CN 202010617829A CN 111796802 B CN111796802 B CN 111796802B
- Authority
- CN
- China
- Prior art keywords
- component
- package
- target
- service
- type
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/22—Procedural
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- 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
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention discloses a function package generation method, a device and electronic equipment. One embodiment of the method comprises the following steps: determining a target package component to be called by a service interface component from at least two package components according to the type of the target function package in the issued instruction, wherein the package component corresponds to the type of the function package, and the package component is used for calling the service component, and the function package is used for being combined with an application program so that the application program can obtain service functions provided by the function package; and generating a target function packet corresponding to the type of the target function packet according to the service interface component, the target packaging component and the service component. Thus, a new way of generating the target function package is provided.
Description
Technical Field
The disclosure relates to the technical field of internet, and in particular relates to a method and a device for generating a functional package and electronic equipment.
Background
With the development of the internet, users increasingly use functions of terminal devices, so that work and life are more convenient. As application programs become more and more engineered and services become more and more massive, componentization is a convenient engineering architecture. In some application scenarios, we use each service as a component and develop and release it independently. For example, a live application may have multiple components, such as a live component, a login component, a sharing component, a private letter component, and so forth. To reduce the size of the feature pack or to implement dynamic updating of the components, some components may be plugin, the default application package does not contain the business module plugin, but rather the business plugin is downloaded as needed when used by the user.
Disclosure of Invention
This disclosure is provided in part to introduce concepts in a simplified form that are further described below in the detailed description. This disclosure is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
In a first aspect, an embodiment of the present disclosure provides a method for generating a function package, including: determining a target package component to be called by a service interface component from at least two package components according to the type of the target function package in the issued instruction, wherein the package component corresponds to the type of the function package, and the package component is used for calling the service component, and the function package is used for being combined with an application program so that the application program can obtain service functions provided by the function package; and generating a target function packet corresponding to the type of the target function packet according to the service interface component, the target packaging component and the service component.
In a second aspect, an embodiment of the present disclosure provides a function packet generating apparatus, including: the determining unit is used for determining a target package component to be called of the service interface component from at least two package components according to the type of the target function package in the issuing instruction, wherein the package component corresponds to the type of the function package, the package component is used for calling the service component, and the function package is used for being combined with the application program so that the application program can obtain the service function provided by the function package; and the generating unit is used for generating a target function packet corresponding to the type of the target function packet according to the service interface component, the target packaging component and the service component.
In a third aspect, an embodiment of the present disclosure provides an electronic device, including: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method as described in the first aspect.
In a fourth aspect, embodiments of the present disclosure provide a computer readable medium having stored thereon a computer program which, when executed by a processor, implements the first aspect.
It should be noted that, by setting at least two kinds of packaging components, different packaging components call service components to generate different types of functional packages. Therefore, different functional packages can be generated under the condition of developing one service component, the workload of developers is reduced, and the development period and cost of the functional packages are reduced.
Drawings
The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.
FIG. 1 is a flow chart of one embodiment of a method of feature packet generation according to the present disclosure;
fig. 2 is an application scenario diagram according to the present disclosure.
FIG. 3 is a schematic diagram of the structure of one embodiment of a rights control apparatus in accordance with the present disclosure;
FIG. 4 is an exemplary system architecture to which the feature pack generation method or rights control method of one embodiment of the present disclosure may be applied;
fig. 5 is a schematic diagram of a basic structure of an electronic device provided according to an embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.
It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.
It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.
The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.
Referring to fig. 1, a flow of one embodiment of a method of generating a feature packet according to the present disclosure is shown. The function package generating method is applied to the server. The method for generating the functional package as shown in fig. 1 comprises the following steps:
and step 101, determining a target packaging component to be called by the service interface component according to the type of the target functional package in the issued instruction.
In this embodiment, the execution body (e.g., the server) of the function package generating method may determine, according to the type of the target function package in the issue instruction, a target wrapper component to be invoked by the service interface component.
In this embodiment, the execution body may respond to the instruction issued by the user, and then perform a series of steps such as packaging, compiling, and the like, to generate the execution generation target function package.
In this embodiment, the above-described issue instruction may be used to instruct generation of a function package to be generated.
In some application scenarios, a user may enter publication mode information and then confirm the publication. The instruction body may acquire the target package type based on the distribution mode information input from the user after the user confirms the distribution. The issue mode information and the operation of confirming the issue can be understood as an issue instruction. Since release is a conventional means in the field of computer software, no further description will be given here.
Here, the feature pack is used in combination with an application program so that the application program can obtain service functions provided by the feature pack. The feature pack may be used to implement relatively independent functions. The feature pack may have independent versions and may be compiled, tested, packaged, and deployed independently. The function package can be combined with the application through hot plug, and the functions of the application are expanded.
In some application scenarios, the function package may be called a function module, that is, applications are divided according to functions, and codes for implementing the same function are integrated together, so that the functions of the module are relatively complex, but all belong to the same service. For example, business modules (i.e., packages) of different types may be divided according to project functional requirements, such as registration, login, take-out, live, etc.
In this embodiment, the division basis and specific types of the function package types may be set according to the actual application scenario, which is not limited herein.
In some application scenarios, the above-mentioned function package types may be divided according to different packaging and introduction manners. As an example, the feature pack type may include, but is not limited to, at least one of: the import library type (Android aar), the plug-in type, jar (Java Archive) type.
In some application scenarios, jar contains a compiled class file and some text files containing metadata.
In some application scenarios, aar is more Android-specific files than jar, such as layout files, extensible files, and manifest files. In other words, one aar is a complete Module in Android.
In some application scenarios, plug-in type may refer to the type of interaction with the main program through the plug-in. The plug-in type package marks its identity by implementing an extended contract (typically an interface) specified by the host program and receives event responses from the host program. Interaction with the main program is achieved by mobilizing services provided by the main program.
In the present embodiment, a required component may be issued in the component repository in advance. The type of the distributed component may be set as needed, and is not limited herein.
Here, the component repository may be a project management and automation build tool, such as Maven repository, ivy repository. The place where the component packages are stored in a concentrated way is the component warehouse. The component warehouse can be locally placed or can be placed on a certain remote server. Either private warehouses or public.
In some application scenarios, business components and business interface components may be published in advance in a component repository.
In some application scenarios, packaging components may also be published in a component repository. The package assembly may be a generic term for various types of package assemblies.
In this embodiment, the service interface component may be an interface module provided by the functional component externally. External may refer herein to other functional components in the application.
Here, the business interface component may define some parameters in accordance with conventions with the host application. By way of example, the feature pack is a login feature pack, and the business interface component in the login feature pack may define parameters such as an account, password, etc.
In this embodiment, the wrapper component may be used to invoke a service component, and the wrapper component may correspond to a function package type.
In some application scenarios, the wrapper component may include a first wrapper component and a second wrapper component. The first wrapper component may correspond to a reference library type. In some embodiments, the second package component may correspond to a plug-in type.
In this embodiment, the service component may be used to implement a service function. I.e. the service component may be a core implementation component of the service logic. Either the first wrapper component or the second wrapper component invokes the business component.
As an example, the business component can include a login component. The login component may be used to implement the business logic of login.
In the present embodiment, a package component corresponding to the target function package type may be determined as the target package component. As an example, if the type of the target functional packet in the issued instruction is an AAR type, the wrapper component corresponding to the AAR type may be determined as the target wrapper component.
And 102, generating a target function package corresponding to the target package type according to the service interface component, the target package component and the service component.
In this embodiment, the executing body may issue the target function package corresponding to the target package type according to the service interface component, the target package component, and the service component.
Here, the executing body may establish a call relationship of the service interface component to call the target wrapper component, and establish a call relationship of the target wrapper component to call the service component. And compiling the components of the path of the business interface component, the target packaging component and the business component to generate a target function package.
It should be noted that, in the method for generating a functional package provided in this embodiment, by setting at least two package components, different package components call service components to generate different types of functional packages. Therefore, different functional packages can be generated under the condition of developing one service component, and the application can flexibly select the functional packages suitable for the application according to actual requirements because different types of functional packages can have different characteristics (such as whether the application can be updated thermally or not). Therefore, various functional packages can be generated to flexibly meet the requirements, the workload of developers is reduced, and the development period and cost of the functional packages are reduced.
In contrast, in some implementations, because each type of feature pack is tightly coupled to the development framework, different types of feature packs are developed in an independent development manner. Thus, business components of the same function may have repetitive labor between development processes due to the different development frameworks that different types of feature packs rely on.
In some embodiments, the target function package is introduced by: determining a function package to be introduced according to the function package identification in the introduction relation information; and establishing a corresponding relation between the functional package to be introduced and the target application.
In some application scenarios, after the target function package is generated, the target function package may be published to a component repository by the execution body. I.e. the target function package is also introduced as a component supply in the component repository.
In some application scenarios, a feature package may be introduced by an application. The application introducing the target function package may mean that the electronic device on which the application operates may operate the target function package, and communication may be performed between the target function package and the application, where the target function package assists the application in implementing the function of the target function package.
Here, the above-described introduction relation information may indicate a function package to be introduced. The incoming relationship information may be entered by an application developer. The application end developer can acquire the function package corresponding to the target application according to the requirement, and establish the relation between the acquired function package and the target application.
In some application scenarios, the generated feature packages may include AAR-type feature packages and plug-in-type feature packages. An application side (e.g., an application side of an X application) developer may write a function package identifier (e.g., a function package of an AAR type) to be introduced in the introduction relation information. Then, the electronic device used by the application end developer can acquire the function package to be introduced, and establish the corresponding relation between the AAR type function package and the X application. Therefore, the server side of the X application can issue an AAR type function package for the client side of the X application to download and install.
It should be noted that, according to the function package identifier in the introduction relation information, the function package to be introduced is determined, so that the application party can flexibly and conveniently switch the function package to be introduced. As an example, the generated feature packages may include AAR type feature packages and plug-in type feature packages, and an application developer (e.g., an X application) may conveniently switch between the AAR type feature packages and the plug-in type feature packages by modifying the feature package identification in the incoming relationship information.
In some embodiments, the above method may further comprise: the target function package is published to the component repository. Thus, the target function package can be conveniently led into the client of the application by the application developer.
Referring to fig. 2, a schematic diagram of the architecture of the components is shown.
In fig. 2, the service interface component 201 is an interface module provided externally by a function package.
As an example, a login method may be defined in the business interface component.
In fig. 2, service component 202 is the core implementation module of the service logic of the service module, and is invoked in the AAR mode or the plug-in mode. The business components may define functional fields therein, interact with servers, etc.
As an example, the core logic of the login and server interactions, etc. may be defined in the business component.
In fig. 2, the first wrapper component 203 may be an AAR-style outer wrapper class, in effect, a call service component.
In fig. 2, the second wrapper component 204 may be an outer wrapper class in the form of a plug-in, and the plug-in component 205 is a real plug-in module, and the business component may be invoked inside the plug-in component. The first package component and the plug-in component communicate by way of Inter-process communication (Inter-Process Communication, IPC); by way of example, communication may be by way of bonding (Binder) or reflection, etc.
Through the architecture shown in fig. 2, a service developer only needs to write service logic in a service component, and if an interface needs to be exposed externally, the service component needs to be implemented in a service interface component, a first package component, a second package component and a plug-in component.
In some embodiments, the method further comprises: and publishing the first packaging component to the component warehouse, wherein the first packaging component corresponds to the type of the reference library, and the first packaging component is used for calling the business component.
In some embodiments, the step 102 may include: in response to determining that the target wrapper component comprises a first wrapper component, establishing a call relationship of the business interface component to the first wrapper component, and establishing a call relationship of the first wrapper component to the business component; a target feature package is generated that includes a business interface component, a first wrapper component, and a business component.
Here, the target wrapper component includes a first wrapper component, which may be understood as including a reference library type in the issued instruction.
Referring to fig. 2, the target function package including the service interface component, the first wrapper component, and the service component may be a function package along the call path 201, 203, and 202.
It should be noted that, by publishing the first wrapper component to the component repository, the business interface component may be facilitated to refer to the first wrapper component to generate the target function package.
In some embodiments, the above method may further comprise: publishing the plug-in components to a component warehouse, wherein the plug-in components are used for calling service components; and publishing the second package component to the component warehouse, wherein the second package component corresponds to the type of the plug-in component, and the second package component is used for calling the business component through the plug-in component.
In some embodiments, the step 102 may include: in response to determining that the target package component comprises a second package component, establishing a call relationship of the business interface component to the second package component, establishing a call relationship of the second package component to the plug-in component, and establishing a call relationship of the plug-in component to the business component; a target function package is generated that includes a business interface component, a second package component, a plug-in component, and a business component.
Here, the target wrapper component includes a first wrapper component, which may be understood as including a plug-in type in the issued instruction.
Referring to fig. 2, the target function package including the service interface component, the second package component, the plug-in component, and the service component may be a function package along the call path 201, 204, 205, and 202.
It should be noted that, by publishing the second package component to the component repository, the business interface component may be facilitated to refer to the second package component to generate the target function package.
With further reference to fig. 3, as an implementation of the method shown in the foregoing figures, the present disclosure provides an embodiment of a function package generating apparatus, where an embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 1, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 3, the function packet generating device of the present embodiment includes: a determination unit 301 and a generation unit 302; the system comprises a determining unit, a service interface component, a service component and an application program, wherein the determining unit is used for determining a target package component to be called of the service interface component from at least two package components according to a target function package type in an issued instruction, the package component corresponds to the function package type, the package component is used for calling the service component, and the function package is used for being combined with the application program so that the application program can obtain service functions provided by the function package; and the generating unit is used for generating a target function packet corresponding to the type of the target function packet according to the service interface component, the target packaging component and the service component.
In this embodiment, the specific processes of the determining unit 301 and the generating unit 302 of the function packet generating device and the technical effects thereof may refer to the descriptions related to the steps 101 and 102 in the corresponding embodiment of fig. 1, and are not repeated here.
In some embodiments, the feature package type includes a reference library type; the apparatus is further for: and publishing the first packaging component to the component warehouse, wherein the first packaging component corresponds to the type of the reference library, and the first packaging component is used for calling the business component.
In some embodiments, the generating, according to the service interface component, the target wrapper component and the service component, a target function packet corresponding to the target function packet type includes: in response to determining that the target wrapper component comprises a first wrapper component, establishing a call relationship of the business interface component to the first wrapper component, and establishing a call relationship of the first wrapper component to the business component; a target feature package is generated that includes a business interface component, a first wrapper component, and a business component.
In some embodiments, the feature pack type comprises a plug-in type; the apparatus is further for: publishing the plug-in components to a component warehouse, wherein the plug-in components are used for calling service components; and publishing the second package component to the component warehouse, wherein the second package component corresponds to the type of the plug-in component, and the second package component is used for calling the plug-in component.
In some embodiments, the generating, according to the service interface component, the target wrapper component and the service component, a target function packet corresponding to the target function packet type includes: in response to determining that the target package component comprises a second package component, establishing a call relationship of the business interface component to the second package component, establishing a call relationship of the second package component to the plug-in component, and establishing a call relationship of the plug-in component to the business component; a target function package is generated that includes a business interface component, a second package component, a plug-in component, and a business component.
In some embodiments, the apparatus is further to: and publishing the target function package to a component warehouse.
In some embodiments, the target function package is introduced by: determining a function package to be introduced according to the function package identification in the introduction relation information; and establishing a corresponding relation between the functional package to be introduced and the target application.
Referring to fig. 4, fig. 4 illustrates an exemplary system architecture in which the feature pack generation method of one embodiment of the present disclosure may be applied.
As shown in fig. 4, the system architecture may include terminal devices 401, 402, 403, a network 404, and a server 405. The network 404 is used as a medium to provide communication links between the terminal devices 401, 402, 403 and the server 405. The network 404 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The terminal devices 401, 402, 403 may interact with the server 405 through the network 404 to receive or send messages or the like. Various client applications, such as a web browser application, a search class application, a news information class application, may be installed on the terminal devices 401, 402, 403. The client application in the terminal device 401, 402, 403 may receive the instruction of the user and perform the corresponding function according to the instruction of the user, for example, adding the corresponding information in the information according to the instruction of the user.
The terminal devices 401, 402, 403 may be hardware or software. When the terminal devices 401, 402, 403 are hardware, they may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablet computers, electronic book readers, MP3 players (Moving Picture Experts Group Audio Layer III, dynamic video expert compression standard audio plane 3), MP4 (Moving Picture Experts Group Audio Layer IV, dynamic video expert compression standard audio plane 4) players, laptop and desktop computers, and the like. When the terminal devices 401, 402, 403 are software, they can be installed in the above-listed electronic devices. Which may be implemented as multiple software or software modules (e.g., software or software modules for providing distributed services) or as a single software or software module. The present invention is not particularly limited herein.
The server 405 may be a server that provides various services, for example, receives information acquisition requests sent by the terminal devices 401, 402, 403, and acquires presentation information corresponding to the information acquisition requests in various ways according to the information acquisition requests. And related data showing the information is transmitted to the terminal devices 401, 402, 403.
It should be noted that, the method for generating a functional package provided by the embodiments of the present disclosure may be executed by the terminal device, and accordingly, the functional package generating apparatus may be provided in the terminal devices 401, 402, 403. In addition, the method for generating a functional package provided by the embodiment of the present disclosure may also be executed by the server 405, and accordingly, the functional package generating apparatus may be disposed in the server 405.
It should be understood that the number of terminal devices, networks and servers in fig. 4 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to fig. 5, a schematic diagram of a configuration of an electronic device (e.g., a terminal device or server in fig. 4) suitable for use in implementing embodiments of the present disclosure is shown. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. The electronic device shown in fig. 5 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.
As shown in fig. 5, the electronic device may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 501, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 502 or a program loaded from a storage means 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic apparatus 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
In general, the following devices may be connected to the I/O interface 505: input devices 506 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 507 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 508 including, for example, magnetic tape, hard disk, etc.; and communication means 509. The communication means 509 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. While fig. 5 shows an electronic device having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 509, or from the storage means 508, or from the ROM 502. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing device 501.
It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.
In some implementations, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: determining a target package component to be called by a service interface component from at least two package components according to the type of the target functional package in the issued instruction, wherein the package component corresponds to the type of the functional package and is used for calling the service component;
and generating a target function packet corresponding to the type of the target function packet according to the service interface component, the target packaging component and the service component. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a live stream acquisition request; and determining whether to return the live stream according to the live stream acquisition request.
Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. 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.
The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. Where the name of the element does not constitute a limitation on the element itself in some cases, for example, the determining element may also be described as "the element that determines the target wrapper component to be invoked by the business interface component".
The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).
Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.
Claims (11)
1. A method for generating a functional package, comprising:
determining a target package component to be called by a service interface component from at least two package components according to the type of the target function package in the issued instruction, wherein the package component corresponds to the type of the function package, and the package component is used for calling the service component, and the function package is used for being combined with an application program so that the application program can obtain service functions provided by the function package;
generating a target function package corresponding to the type of the target function package according to the service interface component, the target packaging component and the service component;
wherein the function package type comprises a reference library type and a plugin type;
the target function package comprises a service interface component, a first packaging component and a target function package of the service component, wherein the first packaging component corresponds to the type of the reference library; or the target function package comprises a business interface component, a second package component, a plug-in component and a business component, wherein the second package component corresponds to the plug-in type, and the second package component invokes the business component through the plug-in component.
2. The method of claim 1, wherein the step of determining the position of the substrate comprises,
the method further comprises the steps of:
the first wrapper component is published to a component warehouse.
3. The method of claim 2, wherein generating the target function package corresponding to the target function package type according to the service interface component, the target wrapper component, and the service component comprises:
in response to determining that the target wrapper component comprises a first wrapper component, establishing a call relationship of the business interface component to the first wrapper component, and establishing a call relationship of the first wrapper component to the business component;
a target feature package is generated that includes a business interface component, a first wrapper component, and a business component.
4. The method of claim 1, wherein the step of determining the position of the substrate comprises,
the method further comprises the steps of:
publishing the plug-in components to a component warehouse, wherein the plug-in components are used for calling service components;
and publishing the second package component to the component repository, wherein the second package component is used for calling the business component through the plug-in component.
5. The method of claim 4, wherein generating the target function package corresponding to the target function package type based on the business interface component, the target wrapper component, and the business component comprises:
in response to determining that the target package component comprises a second package component, establishing a call relationship of the business interface component to the second package component, establishing a call relationship of the second package component to the plug-in component, and establishing a call relationship of the plug-in component to the business component;
a target function package is generated that includes a business interface component, a second package component, a plug-in component, and a business component.
6. The method of claim 5, wherein the method further comprises:
and publishing the target function package to a component warehouse.
7. The method according to any of claims 1-6, wherein the target function package is introduced by:
determining a function package to be introduced according to the function package identification in the introduction relation information;
and establishing a corresponding relation between the functional package to be introduced and the target application.
8. A function pack generating apparatus, comprising:
the determining unit is used for determining a target package component to be called of the service interface component from at least two package components according to the type of the target function package in the issuing instruction, wherein the package component corresponds to the type of the function package, the package component is used for calling the service component, and the function package is used for being combined with the application program so that the application program can obtain the service function provided by the function package;
the generating unit is used for generating a target function packet corresponding to the type of the target function packet according to the service interface component, the target packaging component and the service component;
the target function package comprises a service interface component, a first packaging component and a target function package of the service component, wherein the first packaging component corresponds to the type of the reference library; or the target function package comprises a business interface component, a second package component, a plug-in component and a business component, wherein the second package component corresponds to the plug-in type, and the second package component invokes the business component through the plug-in component.
9. The apparatus of claim 8, wherein the targeted functionality package is introduced by:
determining a function package to be introduced according to the function package identification in the introduction relation information;
and establishing a corresponding relation between the functional package to be introduced and the target application.
10. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-7.
11. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010617829.1A CN111796802B (en) | 2020-06-30 | 2020-06-30 | Function package generation method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010617829.1A CN111796802B (en) | 2020-06-30 | 2020-06-30 | Function package generation method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111796802A CN111796802A (en) | 2020-10-20 |
| CN111796802B true CN111796802B (en) | 2023-09-12 |
Family
ID=72809817
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010617829.1A Active CN111796802B (en) | 2020-06-30 | 2020-06-30 | Function package generation method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111796802B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7761848B1 (en) * | 2005-03-15 | 2010-07-20 | Open Invention Network, Llc | Code generator tool for building software applications with reusable components |
| CN107066291A (en) * | 2017-02-09 | 2017-08-18 | 阿里巴巴集团控股有限公司 | Packaging method, device and the equipment of SDK, computer-readable recording medium |
| CN109656538A (en) * | 2017-10-11 | 2019-04-19 | 阿里巴巴集团控股有限公司 | Generation method, device, system, equipment and the medium of application program |
| CN110209416A (en) * | 2019-05-31 | 2019-09-06 | 彩讯科技股份有限公司 | Application software update method, device, terminal and storage medium |
| CN110300165A (en) * | 2019-06-26 | 2019-10-01 | 北京字节跳动网络技术有限公司 | A kind of call method of function program, device, equipment and storage medium |
| CN110688096A (en) * | 2019-09-10 | 2020-01-14 | 平安普惠企业管理有限公司 | Method, device, medium and electronic equipment for constructing application program containing plug-in |
| CN111142972A (en) * | 2019-12-27 | 2020-05-12 | 京东数字科技控股有限公司 | Method, apparatus, system, and medium for extending functions of application program |
| CN111158674A (en) * | 2019-12-30 | 2020-05-15 | 广州市百果园信息技术有限公司 | Component management method, system, device and storage medium |
| CN111240657A (en) * | 2020-01-17 | 2020-06-05 | 北京字节跳动网络技术有限公司 | Method and device for generating SDK and electronic equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190196793A1 (en) * | 2017-12-22 | 2019-06-27 | Sap Se | Building enterprise mobile applications |
-
2020
- 2020-06-30 CN CN202010617829.1A patent/CN111796802B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7761848B1 (en) * | 2005-03-15 | 2010-07-20 | Open Invention Network, Llc | Code generator tool for building software applications with reusable components |
| CN107066291A (en) * | 2017-02-09 | 2017-08-18 | 阿里巴巴集团控股有限公司 | Packaging method, device and the equipment of SDK, computer-readable recording medium |
| CN109656538A (en) * | 2017-10-11 | 2019-04-19 | 阿里巴巴集团控股有限公司 | Generation method, device, system, equipment and the medium of application program |
| CN110209416A (en) * | 2019-05-31 | 2019-09-06 | 彩讯科技股份有限公司 | Application software update method, device, terminal and storage medium |
| CN110300165A (en) * | 2019-06-26 | 2019-10-01 | 北京字节跳动网络技术有限公司 | A kind of call method of function program, device, equipment and storage medium |
| CN110688096A (en) * | 2019-09-10 | 2020-01-14 | 平安普惠企业管理有限公司 | Method, device, medium and electronic equipment for constructing application program containing plug-in |
| CN111142972A (en) * | 2019-12-27 | 2020-05-12 | 京东数字科技控股有限公司 | Method, apparatus, system, and medium for extending functions of application program |
| CN111158674A (en) * | 2019-12-30 | 2020-05-15 | 广州市百果园信息技术有限公司 | Component management method, system, device and storage medium |
| CN111240657A (en) * | 2020-01-17 | 2020-06-05 | 北京字节跳动网络技术有限公司 | Method and device for generating SDK and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| 基于Android软件开发组件化研究;殷涛;《计算机应用与软件》;第36卷(第9期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111796802A (en) | 2020-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112286529B (en) | Front-end page development method, device, equipment and storage medium | |
| CN111338623B (en) | Method, device, medium and electronic equipment for developing user interface | |
| CN111367516B (en) | Application interface generation method and device and electronic equipment | |
| CN111930534A (en) | Data calling method and device and electronic equipment | |
| CN111309375B (en) | Method, device, medium and electronic equipment for generating remote procedure call toolkit | |
| CN111324376B (en) | Function configuration method, device, electronic equipment and computer readable medium | |
| CN111309304A (en) | Method, device, medium and electronic equipment for generating IDL file | |
| CN112416303B (en) | Software development kit hot repair method and device and electronic equipment | |
| CN111209205B (en) | Configuration method, configuration device and electronic equipment | |
| CN113391860B (en) | Service request processing method and device, electronic equipment and computer storage medium | |
| CN113407165A (en) | SDK generation and self-upgrade method, device, readable medium and equipment | |
| CN111796802B (en) | Function package generation method and device and electronic equipment | |
| CN111309323B (en) | Parameter initialization method and device and electronic equipment | |
| CN113835790B (en) | Paging page display method and device based on Android | |
| CN111382381B (en) | User data sharing method and device, mobile terminal and storage medium | |
| CN112306469A (en) | Barrier-free component construction method, device, equipment and storage medium | |
| CN110099122B (en) | Method and apparatus for sending network request | |
| CN111694679B (en) | Message processing method and device and electronic equipment | |
| CN115878586B (en) | IPFS storage encapsulation method and device, electronic equipment and readable storage medium | |
| CN115309410B (en) | Edge cluster application publishing method and device of edge computing scene and electronic equipment | |
| CN110750242B (en) | File deployment method, system, medium and electronic equipment | |
| CN111381898B (en) | Interface calling method and device, mobile terminal and storage medium | |
| CN117234574A (en) | Service data acquisition method and device, electronic equipment and storage medium | |
| CN116594630A (en) | File generation method, device, medium and electronic equipment | |
| CN117112023A (en) | Application program packaging method, device, equipment and medium |
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 |