CN110413349B - Service calling method and device, electronic equipment and storage medium - Google Patents
Service calling method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN110413349B CN110413349B CN201910706899.1A CN201910706899A CN110413349B CN 110413349 B CN110413349 B CN 110413349B CN 201910706899 A CN201910706899 A CN 201910706899A CN 110413349 B CN110413349 B CN 110413349B
- Authority
- CN
- China
- Prior art keywords
- service
- application
- application program
- interface
- calling
- 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
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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
- Stored Programmes (AREA)
Abstract
The utility model provides a service calling method, including obtaining first call request, first call request is used for calling the first service of first application program, based on first call request, carries out first processing operation and generates first session data, obtains second call request, second call request is used for calling the second service of second application program, and based on second call request, obtains first session data and carries out second processing operation. The disclosure also provides a service calling device, an electronic device and a computer readable storage medium.
Description
Technical Field
The disclosure relates to a service calling method, a service calling device, an electronic device and a storage medium.
Background
In the background application service system, a scenario that a service framework needs to be switched as a whole due to technical hindrance or business may be encountered. In the switching and migrating process, how to ensure that the migration cost is the lowest, the influence on stock business transaction is the minimum, and the influence on the user interaction flow is not influenced is a problem to be solved urgently.
Disclosure of Invention
One aspect of the present disclosure provides a service invocation method, including obtaining a first invocation request for invoking a first service of a first application, executing a first processing operation and generating first session data based on the first invocation request, obtaining a second invocation request for invoking a second service of a second application, and obtaining the first session data and executing a second processing operation based on the second invocation request.
Optionally, the first application program and the second application program are encapsulated in the same package, and when the package is run, a service process is generated.
Optionally, the first application program and the second application program are each encapsulated as a war package, and the war packages of the first application program and the second application program are collectively encapsulated as an ear package.
Optionally, the second call request is a call request applicable to a first interface of the first application, the first interface is configured to provide the second service, and obtaining the first session data and performing the second processing operation based on the second call request includes converting the second call request into a third call request applicable to a second interface of the second application, the second interface is configured to provide the second service, calling the second interface to call the second service of the second application based on the third call request, accessing and reading the first session data, and performing the second processing operation.
Another aspect of the present disclosure provides a service invoking apparatus, including a first obtaining module, a first processing module, a second obtaining module, and a second processing module. The first obtaining module is used for obtaining a first calling request, and the first calling request is used for calling a first service of a first application program. And the first processing module is used for executing a first processing operation and generating first session data based on the first calling request. And the second obtaining module is used for obtaining a second calling request, and the second calling request is used for calling a second service of the second application program. And the second processing module is used for obtaining the first session data and executing a second processing operation based on the second call request.
Optionally, the first application and the second application are encapsulated in the same package, and when the package is run, a service process is generated.
Optionally, the first application program and the second application program are each encapsulated as a war package, and the war packages of the first application program and the second application program are collectively encapsulated as an ear package.
Optionally, the second call request is a call request applicable to a first interface of the first application program, the first interface is used to provide the second service, and the second processing module includes a conversion sub-module, a call sub-module, and an execution sub-module. And the conversion submodule is used for converting the second calling request into a third calling request suitable for a second interface of a second application program, and the second interface is used for providing the second service. And the calling submodule is used for calling the second interface to call a second service of the second application program based on the third calling request. And the execution submodule is used for accessing and reading the first session data and executing a second processing operation.
Another aspect of the disclosure provides an electronic device comprising a processor and a memory for storing one or more computer-readable instructions, wherein the one or more computer-readable instructions, when executed by the at least one processor, cause the processor to perform the method as described above.
Another aspect of the disclosure provides a computer readable medium having stored thereon computer readable instructions that, when executed, cause a processor to perform the method as described above.
Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:
FIG. 1 schematically illustrates an exemplary application scenario of the service invocation method and apparatus according to an embodiment of the present disclosure;
FIG. 2 schematically illustrates a flow diagram of a service invocation method according to an embodiment of the present disclosure;
FIG. 3 schematically illustrates a flowchart for obtaining first session data and performing a second processing operation based on a second invocation request, in accordance with an embodiment of the present disclosure;
FIG. 4 schematically shows a block diagram of a service invocation device according to an embodiment of the present disclosure; and
FIG. 5 schematically illustrates a block diagram of a computer system suitable for implementing the service invocation method and system according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that these descriptions are illustrative only and are not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
In those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "a or B" should be understood to include the possibility of "a" or "B", or "a and B".
The embodiment of the disclosure provides a service calling method, which includes obtaining a first calling request, wherein the first calling request is used for calling a first service of a first application program, executing a first processing operation and generating first session data based on the first calling request, obtaining a second calling request, wherein the second calling request is used for calling a second service of a second application program, and obtaining the first session data and executing a second processing operation based on the second calling request.
Fig. 1 schematically illustrates an application scenario of the service invocation method and system according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, the first application 110 is developed based on the first development framework 111, and development cost can be reduced by developing customized functions and interfaces for calling the functions on the basis of the first development framework 111. Here, the part of the customized development is referred to as a first interface layer 112.
For some reasons, there may be a need to migrate an application to another development framework. For example, functionality of the first application 110 is migrated to the application 120 developed based on the second development framework 121. The application program may be redeveloped based on the second development framework 121, but the development cost is too high, and the embodiment of the present disclosure may directly migrate the code of the first interface layer 112 to form the second interface layer 122 by developing one interface conversion layer 123, and the function on the second interface layer 122 is supported by the second development framework 121 through the interface conversion layer 123.
Even so, it is not possible to migrate all functions to the second application at once, requiring a transitional process to gradually migrate the functions to the second application. However, unexpected errors may occur in this process. For example, in the case of using a login interface in a first application and using an inquiry interface in a second application, when a user wants to inquire about an account balance after logging in the first application through the login interface of the first application, the user returns to the login interface because the user has not logged in the second application, and an error occurs. Due to the gap between the application programs, the data of the first application program cannot be accessed by the second application program, and therefore, an effective means for solving the problem is lacked.
Fig. 2 schematically shows a flow chart of a service invocation method according to an embodiment of the present disclosure.
As shown in fig. 2, the method includes operations S210 to S240.
In operation S210, a first invocation request for invoking a first service of a first application is obtained. For example, the login operation is performed by calling an interface of the first application program, in this case, the first call request is a login request, and the first service is a login service of the first application program.
In operation S220, a first processing operation is performed and first session data is generated based on the first call request. For example, after receiving a login request, the first application performs a login verification operation, and finally generates first session data with user login information when the user login is successful. If the user calls other services of the first application program later, the other services can execute corresponding functions after confirming the first session data, and if the first session data is lost, the user is considered not to be logged in, and a login interface is returned.
In operation S230, a second invocation request for invoking a second service of a second application is obtained. For example, the query interface has been migrated to the second application, wishing to use the query interface in the second application, and the second call request may be, for example, a call request to call a query service of the second application.
In operation S240, based on the second call request, the first session data is obtained and a second processing operation is performed.
According to the embodiment of the disclosure, the second application program can acquire the first session data in a certain manner, so that errors are avoided.
According to the embodiment of the disclosure, during development, the first application program and the second application program can be packaged in the same package, and when the package is operated, only one service process is generated. Therefore, when the system allocates the memory space for the service process, the first application program and the second application program both have the right to access the memory space, and the session data generated by the first application program can be obtained by the second application program. The session data generated by the two applications can be directed to the same address, that is, the session data generated by the two applications is read and written at the same address, and the two applications share one set of session data.
According to an embodiment of the disclosure, the first application and the second application may be each encapsulated as a war package, the war packages of the first application and the second application being collectively encapsulated as one ear package.
According to the method, the session data is shared between the first application program and the second application program, so that the problem that the session data is lacked to frequently generate re-login in the application program migration process is avoided.
Fig. 3 schematically illustrates a flow chart for obtaining first session data and performing a second processing operation based on a second call request according to an embodiment of the present disclosure.
According to the embodiment of the present disclosure, the second call request is a call request applicable to a first interface of the first application, and the first interface is configured to provide the second service.
As shown in fig. 3, the method includes operations S310 to S330.
In operation S310, the second call request is converted into a third call request applicable to a second interface of a second application, where the second interface is used for providing the second service.
In operation S320, the second interface is called to call a second service of the second application based on the third call request.
In operation S330, the first session data is accessed and read, and a second processing operation is performed.
According to the embodiment of the present disclosure, the second call request is used to call a third interface of a second application developed based on a second development framework, but has a similar form as the call request used to call a first interface of a first application developed based on the second development framework, wherein the first interface and the third interface are both used to provide a second service. The interface translation layer may translate the second call request into a third call request, and may invoke a second interface developed based on a second development framework. For example, referring to fig. 1, a first interface may be developed on the surface of the first interface layer 112 of the first application 110, a second interface may be developed in the interface translation layer 123 of the second application 120, and a third interface may be developed on the surface of the second interface layer 122 of the second application 120.
For example, a first query interface of a first application requires an incoming A 1 、A 2 Two parameters, the third query interface of the second application also needs to be transferred into A 1 、A 2 Two parameters, and a second query interface of the second application, i.e. based on the second development framework 121 and the interface translation layer 123, needs to input the parameter B 1 、B 2 . Interface translation layer 123 can call A in the request 1 、A 2 Conversion to B 1 、B 2 Thereby realizing the invocation of the inquiry function. The method can greatly reduce the development cost.
Based on the same inventive concept, the present disclosure also provides a service invocation device, and the service invocation device of the embodiment of the present disclosure is described below with reference to fig. 4.
Fig. 4 schematically shows a block diagram of a service invocation device 400 according to an embodiment of the present disclosure.
As shown in fig. 4, the apparatus 400 may include a first obtaining module 410, a first processing module 420, a second obtaining module 430, and a second processing module 440.
The first obtaining module 410, for example, performs operation S210 described above with reference to fig. 2, for obtaining a first call request, the first call request being for calling a first service of a first application.
The first processing module 420, for example, performs operation S220 described above with reference to fig. 2, for performing a first processing operation and generating first session data based on the first call request.
The second obtaining module 430, for example, performs operation S230 described above with reference to fig. 2, for obtaining a second call request, which is used for calling a second service of a second application.
The second processing module 440, for example, performs operation S240 described above with reference to fig. 2, is configured to obtain the first session data and perform a second processing operation based on the second call request.
According to the embodiment of the disclosure, the first application program and the second application program are encapsulated in the same package, and when the package is run, a service process is generated.
According to the embodiment of the disclosure, the first application program and the second application program are respectively encapsulated into a war package, and the war packages of the first application program and the second application program are jointly encapsulated into an ear package.
According to the embodiment of the present disclosure, the second call request is a call request applicable to a first interface of the first application, and the first interface is configured to provide the second service. The second processing module 440 may include a conversion submodule, a calling submodule, and an execution submodule.
The converting submodule, for example, performs operation S310 described above with reference to fig. 3, and is configured to convert the second call request into a third call request applicable to a second interface of a second application, where the second interface is used to provide the second service.
Invoking a submodule, for example performing operation S320 described above with reference to fig. 3, for invoking the second interface to invoke a second service of the second application based on the third invocation request.
The execution submodule, for example, performs operation S330 described above with reference to fig. 3, for accessing and reading the first session data, and performing a second processing operation.
Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or by any other reasonable means of hardware or firmware for integrating or packaging a circuit, or by any one of or a suitable combination of any of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.
For example, any plurality of the first obtaining module 410, the first processing module 420, the second obtaining module 430, the second processing module 440, the converting sub-module, the calling sub-module, and the executing sub-module may be combined and implemented in one module, or any one of the modules may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first obtaining module 410, the first processing module 420, the second obtaining module 430, the second processing module 440, the converting sub-module, the invoking sub-module, and the executing sub-module may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or in a suitable combination of any of them. Alternatively, at least one of the first obtaining module 410, the first processing module 420, the second obtaining module 430, the second processing module 440, the converting sub-module, the invoking sub-module, and the executing sub-module may be implemented at least in part as a computer program module that, when executed, may perform a corresponding function.
FIG. 5 schematically illustrates a block diagram of a computer system suitable for implementing the service invocation methods and apparatus according to embodiments of the present disclosure. The computer system illustrated in FIG. 5 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure. The computer system shown in fig. 5 may be implemented as a server cluster including at least one processor (e.g., processor 501) and at least one memory (e.g., storage portion 508).
As shown in fig. 5, a computer system 500 according to an embodiment of the present disclosure includes a processor 501 that can 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 section 508 into a Random Access Memory (RAM) 503. Processor 501 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 501 may also include on-board memory for caching purposes. Processor 501 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the disclosure.
In the RAM 503, various programs and data necessary for the operation of the system 500 are stored. The processor 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. The processor 501 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 502 and/or the RAM 503. Note that the programs may also be stored in one or more memories other than the ROM 502 and the RAM 503. The processor 501 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the present disclosure, system 500 may also include an input/output (I/O) interface 505, input/output (I/O) interface 505 also being connected to bus 504. The system 500 may also include one or more of the following components connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure 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 computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program, when executed by the processor 501, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable medium, which may be embodied in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer readable medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to embodiments of the present disclosure, a computer readable medium may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination 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 present 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 contrast, in the present disclosure, a computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. 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: wireless, wired, optical fiber cable, radio frequency signals, etc., or any suitable combination of the foregoing.
For example, according to embodiments of the present disclosure, a computer-readable medium may include ROM 502 and/or RAM 503 and/or one or more memories other than ROM 502 and RAM 503 described above.
The flowchart 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 or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It will be appreciated by a person skilled in the art that various combinations or/and combinations of features recited in the various embodiments of the disclosure and/or in the claims may be made, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments of the present disclosure and/or the claims may be made without departing from the spirit and teachings of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the disclosure, and these alternatives and modifications are intended to fall within the scope of the disclosure.
Claims (6)
1. A service invocation method, comprising:
the method comprises the steps of obtaining a first calling request, wherein the first calling request is used for calling a first service of a first application program, and the first application program is developed based on a first development framework;
executing a first processing operation and generating first session data based on the first calling request;
obtaining a second calling request, wherein the second calling request is used for calling a second service of a second application program, the second calling request is a calling request suitable for a first interface of the first application program, the first interface is used for providing the second service, the second application program is developed based on a second development framework, the first application program and the second application program are respectively packaged into a war package, and the war packages of the first application program and the second application program are jointly packaged into an ear package;
converting the second call request into a third call request applicable to a second interface of a second application program, wherein the second interface is used for providing the second service;
based on the third call request, calling the second interface to call a second service of the second application; and
accessing and reading the first session data and performing a second processing operation.
2. The method of claim 1, wherein the first application and the second application are encapsulated in a same package, and wherein a service process is generated when the package is run.
3. A service invocation apparatus, comprising:
the system comprises a first obtaining module, a first service module and a second obtaining module, wherein the first obtaining module is used for obtaining a first calling request, the first calling request is used for calling a first service of a first application program, and the first application program is developed based on a first development framework;
the first processing module is used for executing a first processing operation and generating first session data based on the first calling request;
a second obtaining module, configured to obtain a second call request, where the second call request is used to call a second service of a second application, the second call request is a call request applicable to a first interface of the first application, the first interface is used to provide the second service, the second application is developed based on a second development framework, the first application and the second application are each encapsulated as a war package, and the war packages of the first application and the second application are jointly encapsulated as an ear package;
a conversion submodule, configured to convert the second call request into a third call request applicable to a second interface of a second application program, where the second interface is used to provide the second service;
a calling submodule, configured to call the second interface to call a second service of the second application program based on the third call request; and
and the execution submodule is used for accessing and reading the first session data and executing a second processing operation.
4. The apparatus of claim 3, wherein the first application and the second application are encapsulated in a same package, and wherein a service process is generated when the package is run.
5. An electronic device, comprising:
a processor; and
a memory having computer readable instructions stored thereon that, when executed by the processor, cause the processor to perform the method of any of claims 1-2.
6. A computer readable storage medium having computer readable instructions stored thereon, which when executed by a processor, cause the processor to perform the method of any one of claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910706899.1A CN110413349B (en) | 2019-07-31 | 2019-07-31 | Service calling method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910706899.1A CN110413349B (en) | 2019-07-31 | 2019-07-31 | Service calling method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110413349A CN110413349A (en) | 2019-11-05 |
| CN110413349B true CN110413349B (en) | 2022-10-14 |
Family
ID=68365234
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910706899.1A Active CN110413349B (en) | 2019-07-31 | 2019-07-31 | Service calling method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110413349B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105338063A (en) * | 2015-09-30 | 2016-02-17 | 北京奇虎科技有限公司 | Multi-server user session sharing method and device |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1783780B (en) * | 2004-12-04 | 2010-09-08 | 华为技术有限公司 | Method and device for realizing domain authorization and network authority authorization |
| US20080282258A1 (en) * | 2007-05-10 | 2008-11-13 | Research In Motion Limited | Sharing the common session between two applications on the same server |
| CN102622229A (en) * | 2012-02-24 | 2012-08-01 | 北京星网锐捷网络技术有限公司 | Fusion method, fusion system and fusion device of development frameworks of different types |
| US9578111B2 (en) * | 2012-06-08 | 2017-02-21 | International Business Machines Corporation | Enabling different client contexts to share session information |
| CN102779071A (en) * | 2012-06-14 | 2012-11-14 | 华为技术有限公司 | Method, device and system for calling software interface |
| FR3021831A1 (en) * | 2014-06-03 | 2015-12-04 | Orange | METHOD AND DEVICE FOR APPLICATION SHARING |
| US10069814B2 (en) * | 2014-10-28 | 2018-09-04 | Ca, Inc. | Single sign on across multiple devices using a unique machine identification |
| CN107306290B (en) * | 2016-04-22 | 2021-06-18 | 中国移动通信集团重庆有限公司 | Session sharing method and application server |
| CN107347068A (en) * | 2017-07-10 | 2017-11-14 | 恒生电子股份有限公司 | Single-point logging method and system, electronic equipment |
| CN109213519B (en) * | 2018-09-14 | 2020-01-03 | 北京数聚鑫云信息技术有限公司 | Heterogeneous API adaptation processing method and system |
| CN109150913B (en) * | 2018-10-17 | 2020-12-18 | 东软集团股份有限公司 | Method and device for accessing application under micro-service architecture, storage medium and server |
-
2019
- 2019-07-31 CN CN201910706899.1A patent/CN110413349B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105338063A (en) * | 2015-09-30 | 2016-02-17 | 北京奇虎科技有限公司 | Multi-server user session sharing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110413349A (en) | 2019-11-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032706B (en) | Intelligent contract execution method, device, equipment and storage medium | |
| CN111309304B (en) | Method, device, medium and electronic equipment for generating IDL file | |
| CN113132400B (en) | Business processing method, device, computer system and storage medium | |
| CN113835842A (en) | Service design method and system for simultaneously supporting monomer architecture and micro-service architecture | |
| CN110968433A (en) | Information processing method and system and electronic equipment | |
| CN110413349B (en) | Service calling method and device, electronic equipment and storage medium | |
| CN111414154A (en) | Method and device for front-end development, electronic equipment and storage medium | |
| CN113535565B (en) | Interface use case generation method, device, equipment and medium | |
| CN115562887A (en) | Inter-core data communication method, system, device and medium based on data package | |
| CN112506781B (en) | Test monitoring method, device, electronic equipment, storage medium and program product | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN113760262A (en) | Task processing method, device, computer system and computer readable storage medium | |
| CN109669720B (en) | Chain type asynchronous request processing method and device based on Promise and electronic equipment | |
| CN113176907A (en) | Interface data calling method and device, computer system and readable storage medium | |
| CN112068814A (en) | Method, device, system and medium for generating executable file | |
| CN113282391B (en) | Cluster switching method, cluster switching device, electronic equipment and readable storage medium | |
| CN112688863B (en) | Gateway data processing method and device and electronic equipment | |
| CN113347250B (en) | Data access method, data access device, electronic equipment and readable storage medium | |
| CN115225916B (en) | Video processing method, device and equipment | |
| US11748236B2 (en) | Multi-user debugging with user data isolation | |
| CN115297169B (en) | Data processing method, device, electronic equipment and medium | |
| CN109246177B (en) | Method for designing asynchronous communication tool in Android | |
| CN110633155A (en) | Communication method, device, medium and electronic equipment of plug-in framework | |
| CN115423448A (en) | Service processing method and device, electronic equipment and storage medium | |
| CN113051090A (en) | Interface processing method and device, interface calling method and device, system 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 |