CN111782413A - Cross-application component communication method and device - Google Patents
Cross-application component communication method and device Download PDFInfo
- Publication number
- CN111782413A CN111782413A CN201910272410.4A CN201910272410A CN111782413A CN 111782413 A CN111782413 A CN 111782413A CN 201910272410 A CN201910272410 A CN 201910272410A CN 111782413 A CN111782413 A CN 111782413A
- Authority
- CN
- China
- Prior art keywords
- component
- app
- type
- url
- parameter
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000004891 communication Methods 0.000 title abstract description 38
- 230000001960 triggered effect Effects 0.000 claims abstract description 11
- 230000008569 process Effects 0.000 claims description 11
- 230000000694 effects Effects 0.000 abstract description 6
- 230000006870 function Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 7
- 238000012544 monitoring process Methods 0.000 description 7
- 238000011161 development Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000008447 perception Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000011900 installation process Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a cross-application component communication method and device, and the method comprises the following steps: when detecting that a first type component of a first APP is triggered, acquiring a calling parameter of the first type component, and sending the calling parameter to a second type component of the first APP; controlling the second type of component to generate a URL according to the calling parameter; sending the URL to a second APP through a second type of component; the second type of component is a component which is simulated in advance according to the first type of component of the second APP. When acquiring the calling parameter of the first type of component, whether cross-APP communication is required to be sensed or not is avoided, the calling parameter is directly sent to the second type of component according to the situation in the same APP, the URL is created by the second type of component based on the calling parameter, and the created URL is sent to the second APP, so that the first type of component in the first APP can be used for calling the first type of component in the second APP without sensing, and the cross-APP communication effect is good.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for component communication across application programs.
Background
At present, modular architecture development is generally adopted for development of an APP (application program), namely, the APP is composed of a plurality of components and a middleware, each component completes a service, the service can provide a plurality of services, and communication among the components in the APP is decoupled and forwarded through the middleware. For a component needing to communicate across APPs, a URL (Uniform Resource Locator) splicing rule of an APP to which a called component belongs needs to be maintained inside the component. When the component needs to call another component, whether the component and the other component are in the same APP needs to be judged, if not, the URL splicing rule of the APP to which the other component belongs is searched, the URL is created according to the URL splicing rule and by using the calling parameter of the other component, the created URL is sent to the APP to which the other component belongs, and the APP to which the other component belongs analyzes and executes the URL according to the pre-negotiated analysis rule, so that the calling of the other component is realized.
Therefore, many components in the APP need to communicate with components in other APPs in a cross-APP manner, and for each component in the APP, whether the component and the called component are in the same APP needs to be sensed first when the other components are called, and if not, a URL splicing rule needs to be sensed and a URL is created, so that a cross-APP communication effect is poor.
Disclosure of Invention
In view of this, the present application provides a cross-application component communication method and apparatus, so as to solve the problem of poor cross-APP communication effect in the related art.
According to a first aspect of embodiments of the present application, there is provided a method for component communication across applications, the method comprising:
when detecting that a first type component on a first APP is triggered, acquiring a calling parameter of the first type component, and sending the calling parameter to a second type component on the first APP;
controlling the second type of component to generate a URL (uniform resource locator) for accessing a second APP according to the calling parameter;
sending, by the second class component, the URL from the first APP to the second APP;
the first-class component is used for calling the function realized by the first-class component on the second APP, and the second-class component is simulated in advance according to the first-class component in the second APP.
According to a second aspect of embodiments of the present application, there is provided a component communication apparatus across applications, the apparatus comprising:
the parameter sending module is used for acquiring a calling parameter of a first type of component when detecting that the first type of component on a first APP is triggered, and sending the calling parameter to a second type of component on the first APP;
the URL generation module is used for controlling the second type of component to generate a URL for accessing the second APP according to the calling parameter;
an access module for sending the URL from the first APP to the second APP via the second class component;
the first-class component is used for accessing the function realized by the first-class component on the second APP, and the second-class component is simulated in advance according to the first-class component in the second APP.
According to a third aspect of embodiments herein, there is provided an electronic device, the device comprising a readable storage medium and a processor;
wherein the readable storage medium is configured to store machine executable instructions;
the processor is configured to read the machine executable instructions on the readable storage medium and execute the instructions to implement the steps of the method according to the first aspect.
By applying the embodiment of the application, when the first type of component on the first APP is detected to be triggered, the calling parameter is obtained and sent to the second type of component on the first APP, then the second type of component is controlled to generate the URL for accessing the second APP according to the calling parameter, and the generated URL is sent to the second APP from the first APP through the second type of component.
Based on the above description, when obtaining the calling parameter of the first type of component, it is not necessary to perceive whether the communication is cross-APP communication, and the calling parameter is directly sent to the second type of component according to the scene in the same APP, the second type of component creates the URL based on the calling parameter, and sends the created URL to the second APP, so that the first type of component in the first APP can invoke the first type of component in the second APP without perception, and the cross-APP communication effect is good.
Drawings
FIG. 1 is a diagram illustrating component communication across application programs for a related art implementation according to an illustrative embodiment of the present application;
FIG. 2A is a flow diagram illustrating an embodiment of a method for cross-application component communication according to an illustrative embodiment of the present application;
FIG. 2B is a diagram illustrating component communication across applications according to the embodiment shown in FIG. 2A;
FIG. 3 is a diagram illustrating a hardware configuration of an electronic device according to an exemplary embodiment of the present application;
FIG. 4 is a block diagram illustrating an embodiment of a cross-application component communication device according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
As shown in fig. 1, an APP1 is composed of an access control component, an event component, a parking lot component and middleware, an APP2 is composed of a video component and middleware, assuming that the access control component in APP1 receives an externally triggered call request, the access control component determines whether an APP identifier (APP2) in a call parameter carried in the call request is consistent with an APP identifier (APP1) of an APP to which the access control component belongs, if not, the access control component finds a URL splicing rule corresponding to APP2 from the component, creates a URL according to the URL splicing rule and the call parameter, sends the created URL to APP2 by using an openURL method provided by a call system, analyzes the URL 2 to obtain the call parameter and transmits the call parameter to the middleware on the APP2, assuming that the call parameter is a service for calling a certain monitoring point in real time, the middleware finds the video component and transmits the call parameter to the video component, therefore, the video of a certain monitoring point is previewed.
Based on the above-mentioned cross-APP communication scheme, if many components in APP1 need to communicate with the video component in APP2 in a cross-APP manner, each component in APP1 needs to sense whether the component and the called component are in the same APP, and if not, needs to sense the URL splicing rule and create a URL, and if the URL parsing rule of APP2 changes, each component in APP1 needs to make corresponding changes to the URL splicing rule, so that the cross-APP communication effect is not good.
It is worth noting that for the inter-component communication condition in the same APP, if the access control component judges that the APP identification in the calling parameter carried by the calling request is consistent with the APP identification of the APP to which the access control component belongs, the access control component and the called component are represented in the same APP, the access control component directly transmits the calling parameter to the middleware, the calling parameter is transmitted to the called component (such as a parking lot component) through the middleware, and the called component realizes the service corresponding to the calling parameter.
Based on this, each component in each APP has a corresponding protocol, the protocol declares the service provided by the component, and the protocol is externally disclosed, so that in the process of developing the APPs, which components in which APPs (hereinafter, referred to as second APPs) need to be called can be determined in advance according to the actual requirements of each component in the APPs (hereinafter, referred to as first APPs), the protocols corresponding to the components to be called are obtained from the second APPs, one component is simulated in the first APPs by using the obtained protocols, and meanwhile, a URL creation method is preconfigured in the simulated component. Therefore, when the component in the first APP communicates with other components, whether the component and the called component are in the same APP or not is not required to be sensed, the calling parameter is transmitted to other components (namely, the simulated component) only according to the situation in the same APP, and the URL splicing rule of other APPs is not required to be maintained by the component, so that cross-APP communication can be achieved without sensing.
The component communication method across application programs proposed in the present application is explained in detail below with specific embodiments.
Fig. 2A is a flowchart of an embodiment of a cross-application component communication method according to an exemplary embodiment of the present application, where the cross-application component communication method may be applied to an electronic device installed with a first APP, where the first APP may be composed of a first class component and a second class component, the first class component is used to access a function implemented by the first class component on a second APP, and the second class component is a component that is simulated in advance according to the first class component in the second APP.
In the embodiment of the present application, the first-type component refers to a component that can actually implement a service (i.e., a method), and the first-type component may be a plurality of first components or one first component. For the case of component communication across APP, each two first components in the first class of components may communicate with each other.
As shown in fig. 2A, the cross-application component communication method includes the following steps:
step 201: when detecting that a first type component on a first APP is triggered, obtaining a calling parameter of the first type component.
In an embodiment, in a process that the electronic device runs the first APP, when a certain function module in the first type of component on the first APP is triggered externally, the electronic device generates a function selection instruction according to the trigger, so that the electronic device can receive the function selection instruction from the outside, the function selection instruction carries information of an externally selected target function, and a calling parameter corresponding to the target function is selected from all calling parameters configured by the first type of component.
Illustratively, each component included in the first type of component may implement multiple functions, and a user may select different target functions and may obtain different call parameters correspondingly. The invocation parameters may include APP identification, protocol identification, service identification, and service parameters. The protocol identifier is used for uniquely identifying a component, and the corresponding protocol is used for declaring the service provided by the component, and the protocol can be realized by a class object.
Taking a video component as an example, previewing videos of each monitoring point, calling a camera to take pictures and the like can be selected through the video component, assuming that a user selects previewing videos of a certain monitoring point, calling parameters can include an APP identifier to which the video component belongs, a protocol identifier corresponding to the video component, a preview service identifier and a monitoring point identifier.
It should be noted that, if the first type component in the second APP is called through the first type component, the APP identifier in the calling parameter is the identifier of the second APP, and if the first type component in the present APP is called through the first type component, the APP identifier in the calling parameter is the identifier of the present APP.
Step 202: and sending the calling parameter to a second-class component on the first APP.
In an embodiment, the first APP may further include middleware between the first-class component and the second-class component, so that the middleware may forward the calling parameter to the second-class component by sending the calling parameter to the middleware first.
The calling parameter comprises a protocol identifier, and the second type of component corresponds to the protocol identifier.
For example, if the second class component includes a plurality of second components, the second components may correspond to the protocol identifiers one to one, so that the middleware may obtain the second components corresponding to the protocol identifiers from the second class components and forward the invocation parameters to the second components corresponding to the protocol identifiers.
It should be noted that, for the case of component communication not across APPs, the middleware traverses the first type of component according to the protocol identifier to forward the call parameter to the corresponding first component.
Therefore, when the calling parameters of the first type of component are acquired, the calling parameters are directly transmitted to the middleware according to the scenes in the same APP, whether the component and the called component are in the same APP or not is not required to be sensed, and then the URL is not required to be created according to the URL splicing rule.
Step 203: and controlling the second type of component to generate a URL for accessing a second APP according to the calling parameter.
In an embodiment, since the second type of component belongs to the simulated component, the service of the protocol declaration is not really implemented inside the second type of component, and the service of the protocol declaration is really implemented as a corresponding component in the second APP, the URL creation method is implemented inside the second type of component. Based on the URL, the second type of component can be controlled to splice the parameters related to the URL in the calling parameters according to the configured URL splicing rule to obtain the URL.
And the URL splicing rule is obtained according to the URL analysis rule of the second APP and is configured in the second type of assembly in advance.
In an example, in the installation process of an APP, a user-defined URLSchema is usually registered in advance with an application system, if the APP1 is to transfer data to the APP2, the APP1 needs to create a URL with a URL Schema registered by the APP2, and therefore, when creating the URL, the second type of component may first use the APP identifier included in the call parameter to traverse the registry of the application system to find the URL Schema corresponding to the APP identifier, then use the configured URL splicing rule in the component, and use the found URL Schema to splice parameters related to the URL in the call parameter to obtain the URL.
For example, the URL obtained by splicing is: NSURL myURL ═ NSURL URLWithString @ "App 2:// protocol name? methodName? param "; wherein, NSURL URLWithString @ App 2://' is URL Schema of App2, "protocolName" is protocol identification in calling parameter, "methodName" is service name in calling parameter, and "param" is service parameter in calling parameter.
It should be noted that, since the URL splicing rule configured in the second type of component is obtained in advance according to the URL parsing rule in the second APP, if the parsing rule in the second APP changes, the URL splicing rule configured in the second type of component on the first APP also needs to be changed.
Step 204: sending, by the second class component, the URL from the first APP to the second APP.
In an embodiment, the URL may be sent to the second APP through the second type component by calling an openURL method provided by the application system of the device.
It should be further noted that, when receiving the URL, the second APP parses the URL to obtain a calling parameter and sends the calling parameter to the middleware, and the middleware determines the corresponding first component according to the protocol identifier in the calling parameter and transmits the calling parameter to the first component, so that the first component implements the service corresponding to the calling parameter.
In an exemplary scenario, as shown in fig. 2B, each component (belonging to the first type of component) in APP1 may call a video component in APP2, so during development of APP1, a video component may be simulated in APP1 in advance according to a protocol corresponding to the video component in APP2, and the simulated component (belonging to the second type of component) does not really implement the service of the video component inside, but implements creation of the URL. Suppose that an access control component in APP1 needs to call a video component in APP2 to preview the service of a certain monitoring point, when obtaining the call parameter of the access control component, the call parameter can be directly transferred to the middleware according to the situation in the same APP, the middleware finds a corresponding analog video component according to the protocol identifier in the call parameter, and transfers the call parameter to the analog video component, and controls the analog video component to create a URL, and sends the URL to APP2, APP2 parses the URL to obtain the call parameter and transfers the call parameter to the middleware, the middleware finds a real video component according to the protocol identifier in the call parameter, so that the video component realizes the service corresponding to the call parameter, that is, the video of a certain monitoring point is opened to realize preview.
In the embodiment of the application, when it is detected that a first-class component on a first APP is triggered, a calling parameter of the first-class component is obtained, the calling parameter is sent to a second-class component on the first APP, a URL used for accessing a second APP is generated by controlling the second-class component according to the calling parameter, and the generated URL is sent to the second APP from the first APP through the second-class component.
Based on the above description, when obtaining the calling parameter of the first type of component, it is not necessary to perceive whether the communication is cross-APP communication, and the calling parameter is directly sent to the second type of component according to the scene in the same APP, the second type of component creates the URL based on the calling parameter, and sends the created URL to the second APP, so that the first type of component in the first APP can invoke the first type of component in the second APP without perception, and the cross-APP communication effect is good.
Fig. 3 is a hardware block diagram of an electronic device according to an exemplary embodiment of the present application, where the electronic device includes: a communication interface 301, a processor 302, a machine-readable storage medium 303, and a bus 304; wherein the communication interface 301, the processor 302, and the machine-readable storage medium 303 communicate with each other via a bus 304. The processor 302 may execute the above-described cross-application component communication method by reading and executing machine executable instructions in the machine readable storage medium 303 corresponding to the control logic of the cross-application component communication method, and the specific content of the method is described in the above embodiments and will not be described again here.
The machine-readable storage medium 303 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: volatile memory, non-volatile memory, or similar storage media. In particular, the machine-readable storage medium 303 may be a RAM (random Access Memory), a flash Memory, a storage drive (e.g., a hard drive), any type of storage disk (e.g., an optical disk, a DVD, etc.), or similar storage medium, or a combination thereof.
FIG. 4 is a block diagram of an embodiment of a cross-application component communication device according to an exemplary embodiment of the present application, the component communication device comprising:
a parameter sending module 410, configured to, when it is detected that a first-class component on a first APP is triggered, obtain a calling parameter of the first-class component, and send the calling parameter to a second-class component on the first APP;
a URL generating module 420, configured to control the second class component to generate a URL for accessing the second APP according to the calling parameter;
an access module 430, configured to send, by the second class component, the URL from the first APP to the second APP;
the first-class component is used for calling the function realized by the first-class component on the second APP, and the second-class component is simulated in advance according to the first-class component in the second APP.
In an optional implementation manner, the first APP further includes: middleware between the first type of component and the second type of component;
the parameter sending module 410 is specifically configured to, in the process of sending the calling parameter to the second type component on the first APP, send the calling parameter to the middleware first, so that the middleware forwards the calling parameter to the second type component.
In an optional implementation manner, the invocation parameter includes a protocol identifier, and the second-class component corresponds to the protocol identifier.
In an optional implementation manner, the URL generating module 420 is specifically configured to control the second-class component to splice parameters related to the URL in the invocation parameter according to a configured URL splicing rule to obtain the URL.
In an optional implementation manner, the parameter sending module 410 is specifically configured to receive a function selection instruction from the outside in a process of obtaining a call parameter of the first type component, where the function selection instruction carries information of a target function selected by the outside; and selecting the calling parameter corresponding to the target function from all the calling parameters configured by the first type of component.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It should also be noted that 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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (11)
1. A method of communicating across components of an application, the method comprising:
when detecting that a first type component on a first application program APP is triggered, acquiring a calling parameter of the first type component, and sending the calling parameter to a second type component on the first APP;
controlling the second type of component to generate a Uniform Resource Locator (URL) for accessing a second APP according to the calling parameter;
sending, by the second class component, the URL from the first APP to the second APP;
the first-class component is used for accessing the function realized by the first-class component on the second APP, and the second-class component is simulated in advance according to the first-class component in the second APP.
2. The method of claim 1, wherein said first APP further comprises: middleware between the first type of component and the second type of component;
sending the calling parameter to a second class component on the first APP, including:
and sending the calling parameter to the middleware firstly, so that the middleware forwards the calling parameter to the second type of component.
3. The method according to claim 1 or 2, wherein the invocation parameter includes a protocol identification, and the second-class component corresponds to the protocol identification.
4. The method of claim 1, wherein controlling the second class component to generate a URL for accessing a second APP according to the call parameter comprises:
and controlling the second type of component to splice parameters related to the URL in the calling parameters according to configured URL splicing rules to obtain the URL.
5. The method of claim 1, wherein obtaining invocation parameters for the first class of components comprises:
receiving a function selection instruction from the outside, wherein the function selection instruction carries information of a target function selected from the outside;
and selecting the calling parameter corresponding to the target function from all the calling parameters configured by the first type of component.
6. An apparatus for communicating components across applications, the apparatus comprising:
the parameter sending module is used for acquiring a calling parameter of a first type of component when detecting that the first type of component on a first application program APP is triggered, and sending the calling parameter to a second type of component on the first APP;
the URL generating module is used for controlling the second type of assembly to generate a uniform resource locator URL for accessing the second APP according to the calling parameter;
an access module for sending the URL from the first APP to the second APP via the second class component;
the first-class component is used for accessing the function realized by the first-class component on the second APP, and the second-class component is simulated in advance according to the first-class component in the second APP.
7. The apparatus of claim 6, wherein the first APP further comprises: middleware between the first type of component and the second type of component;
the parameter sending module is specifically configured to send the calling parameter to the middleware first in a process of sending the calling parameter to the second class component on the first APP, so that the middleware forwards the calling parameter to the second class component.
8. The apparatus according to claim 6 or 7, wherein the invocation parameter includes a protocol identifier, and the second-class component corresponds to the protocol identifier.
9. The apparatus according to claim 6, wherein the URL generation module is specifically configured to control the second component to splice parameters related to the URL in the invocation parameters according to configured URL splicing rules to obtain the URL.
10. The apparatus according to claim 6, wherein the parameter sending module is specifically configured to receive a function selection instruction from the outside during the process of obtaining the call parameter of the first class component, where the function selection instruction carries information of an externally selected target function; and selecting the calling parameter corresponding to the target function from all the calling parameters configured by the first type of component.
11. An electronic device, characterized in that the device comprises a readable storage medium and a processor;
wherein the readable storage medium is configured to store machine executable instructions;
the processor configured to read the machine executable instructions on the readable storage medium and execute the instructions to implement the steps of the method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910272410.4A CN111782413B (en) | 2019-04-04 | 2019-04-04 | Cross-application component communication method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910272410.4A CN111782413B (en) | 2019-04-04 | 2019-04-04 | Cross-application component communication method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111782413A true CN111782413A (en) | 2020-10-16 |
| CN111782413B CN111782413B (en) | 2024-02-27 |
Family
ID=72754887
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910272410.4A Active CN111782413B (en) | 2019-04-04 | 2019-04-04 | Cross-application component communication method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111782413B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115499274A (en) * | 2022-09-30 | 2022-12-20 | 中国银行股份有限公司 | Splicing parameter gateway routing method and system, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104052762A (en) * | 2013-03-11 | 2014-09-17 | 腾讯科技（深圳）有限公司 | Data sharing method, device and system |
| US20160313882A1 (en) * | 2015-04-27 | 2016-10-27 | Microsoft Technology Licensing, Llc | Support for non-native file types in web application environment |
| CN107911536A (en) * | 2017-10-27 | 2018-04-13 | 努比亚技术有限公司 | A kind of across application program access method, equipment and computer-readable recording medium |
| CN108255615A (en) * | 2017-11-30 | 2018-07-06 | 平安科技（深圳）有限公司 | Across language call method, server and storage medium |
| CN109412906A (en) * | 2018-10-09 | 2019-03-01 | 南京物联传感技术有限公司 | Across APP program intelligent control interactive system and working method |
-
2019
- 2019-04-04 CN CN201910272410.4A patent/CN111782413B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104052762A (en) * | 2013-03-11 | 2014-09-17 | 腾讯科技（深圳）有限公司 | Data sharing method, device and system |
| US20160313882A1 (en) * | 2015-04-27 | 2016-10-27 | Microsoft Technology Licensing, Llc | Support for non-native file types in web application environment |
| CN107911536A (en) * | 2017-10-27 | 2018-04-13 | 努比亚技术有限公司 | A kind of across application program access method, equipment and computer-readable recording medium |
| CN108255615A (en) * | 2017-11-30 | 2018-07-06 | 平安科技（深圳）有限公司 | Across language call method, server and storage medium |
| CN109412906A (en) * | 2018-10-09 | 2019-03-01 | 南京物联传感技术有限公司 | Across APP program intelligent control interactive system and working method |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115499274A (en) * | 2022-09-30 | 2022-12-20 | 中国银行股份有限公司 | Splicing parameter gateway routing method and system, electronic equipment and storage medium |
| CN115499274B (en) * | 2022-09-30 | 2024-03-22 | 中国银行股份有限公司 | Splicing parameter gateway routing method and system, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111782413B (en) | 2024-02-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109547570B (en) | Service registration method, device, registration center management equipment and storage medium | |
| EP3324601B1 (en) | Development of internet of things (iot) applications | |
| CN102202078B (en) | The method and system of a kind of multiple foreign peoples roles for configuration server field | |
| US20190028360A1 (en) | Visual devops systems and methods | |
| US20170201595A1 (en) | Provisioning iaas services | |
| EP2603855A2 (en) | Integrated information technology service management for cloud resources | |
| EP3516850B1 (en) | Systems and methods for sharing application data between isolated applications executing on one or more application platforms | |
| CN114205342B (en) | Service debugging routing method, electronic equipment and medium | |
| CN109923547B (en) | Program behavior monitoring device, distributed object generation management device, storage medium, and program behavior monitoring system | |
| CN112035122B (en) | Interface deployment method, system and storage medium | |
| US20220357938A1 (en) | Automatically configuring and deploying a software operator in a distributed computing environment from a package | |
| CN111782413A (en) | Cross-application component communication method and device | |
| US20090257085A1 (en) | Generation of a web page including menu items for web pages | |
| WO2015032429A1 (en) | Controlling services deployment in distributed computing systems based on historical use by electronic devices | |
| JP5613255B2 (en) | Application server and method for managing services | |
| CN110943968B (en) | Equipment access control method and equipment access assembly | |
| KR100798916B1 (en) | Method and system for handling the network events in application server using open API based web services | |
| JP6427910B2 (en) | Maintenance environment providing system, maintenance environment providing device, maintenance environment providing method, and program thereof | |
| CN108920277B (en) | Service execution system, method and device and service isolation system | |
| US9027152B2 (en) | Device for right managing web data, recording medium for performing method for right managing web data on computer, and device and method for providing right management information | |
| JP2006236375A (en) | Web application development method, development support system, and program about development method | |
| CN110968817A (en) | Page content detection method, device and system | |
| US11856067B2 (en) | Methods and apparatus to centralize localization of micro-services messages in a distributed cloud environment | |
| CN110430132B (en) | Method and device for binding Socket and VRF | |
| KR101414844B1 (en) | Method and apparatus for moving web object using push |
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 |