CN117061205A - Data interaction method, device and medium for different architecture applications - Google Patents

Data interaction method, device and medium for different architecture applications Download PDF

Info

Publication number
CN117061205A
CN117061205A CN202311111181.0A CN202311111181A CN117061205A CN 117061205 A CN117061205 A CN 117061205A CN 202311111181 A CN202311111181 A CN 202311111181A CN 117061205 A CN117061205 A CN 117061205A
Authority
CN
China
Prior art keywords
message
socket
middleware
receiving end
determining
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.)
Pending
Application number
CN202311111181.0A
Other languages
Chinese (zh)
Inventor
邱纯营
靳庆伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inspur General Software Co Ltd
Original Assignee
Inspur General Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Inspur General Software Co Ltd filed Critical Inspur General Software Co Ltd
Priority to CN202311111181.0A priority Critical patent/CN117061205A/en
Publication of CN117061205A publication Critical patent/CN117061205A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Abstract

The application discloses a data interaction method, equipment and medium for different architecture applications, wherein the method comprises the following steps: determining a plurality of applications and middleware set in a terminal; receiving a Socket encryption message sent by a sending end through a middleware; storing the Socket encrypted message, and forwarding the Socket encrypted message to a receiving end; and analyzing the Socket encryption message based on the appointed form through the receiving end to acquire the interaction message. The system registry does not need to be changed, and the data interaction across the architecture can be completed. As the middleware, the browser internal page application and the local client application to be integrated are not coupled, the browser internal page application and the local client application to be interacted only need to send Socket encryption information to the middleware according to the agreed form of the middleware, the middleware does not sense the content of the information body and feed back corresponding Socket encryption information, and the receiving end can analyze and process the information according to the agreed form with the sending end after receiving the Socket encryption information, so that the data exchange safety is ensured.

Description

Data interaction method, device and medium for different architecture applications
Technical Field
The present application relates to the field of computers, and in particular, to a method, an apparatus, and a medium for data interaction for different architecture applications.
Background
With the deep enterprise informatization, the user office process can use both the local client application of the C/S architecture and the browser application of the B/S architecture. While users may need to pass intermediate results between applications of different architectures when completing tasks supported by different business systems.
In the traditional scheme, a registry protocol can be adopted under a Windows operating system to realize data interaction among different types of applications, the registry protocol is written by a local client application, and a browser side can finish the data interaction by calling a user-defined registry protocol. However, in some systems where the user system rights are severely restricted, there may be situations where the application is not allowed to make registry modifications, and this solution is difficult to implement.
Disclosure of Invention
In order to solve the above problems, the present application proposes a data interaction method for different architecture applications, including:
determining a plurality of applications and middleware, wherein the plurality of applications are arranged in a terminal and at least comprise applications realized through different architectures, and the architectures comprise a C/S architecture and a B/S architecture;
receiving, by the middleware, a Socket encrypted message sent by a sending end, where the sending end belongs to an application in the plurality of applications, and the Socket encrypted message is obtained by encrypting an interaction message based on a contract form;
storing the Socket encryption message, and forwarding the Socket encryption message to a receiving end, wherein the receiving end belongs to one of the applications and is realized by a different structure with the sending end;
and analyzing the Socket encryption message based on the appointed form through the receiving end so as to acquire the interaction message.
In one example, before receiving, by the middleware, the Socket encrypted message sent by the sender, the method further includes:
determining a message parser contained in the middleware;
and providing definition of the message format and meaning rule analysis by the message analyzer so as to generate a contracted form between the sending end and the receiving end based on the definition of the message format and the meaning rule analysis.
In one example, storing the Socket encrypted message specifically includes:
determining a message receiver and a message memory contained in the middleware;
receiving the Socket encryption message through the message receiver, and sending the Socket encryption message to the message memory;
and encrypting the Socket information through the information memory, and continuously storing the classified queues according to the information head.
In one example, forwarding the Socket encrypted message to the receiving end specifically includes:
determining a message sender contained in the middleware;
and extracting the Socket encrypted message according to a first set frequency in the message memory by the message transmitter, transmitting the extracted Socket encrypted message to a receiving end, providing message transmission confirmation information after the Socket encrypted message is transmitted to the receiving end, and providing a retry mechanism after the Socket encrypted message is not successfully transmitted to the receiving end.
In one example, the method further comprises:
providing message queue support through the message memory for high-frequency message interaction to store the Socket encrypted message into the message queue, wherein the high frequency refers to a frequency corresponding to the time when the message interaction times in the preset duration are higher than the preset times;
extracting Socket encryption information according to a second set frequency in the information memory by the information transmitter, and transmitting the extracted Socket encryption information to a receiving end, wherein the second set frequency is faster than the first set frequency;
and providing a retry mechanism after the Socket encrypted message is sent to the receiving end and after the Socket encrypted message is not successfully sent to the receiving end, wherein the corresponding retry times in the retry mechanism are configured based on a message header matching rule.
In one example, the method further comprises:
determining a message monitor contained in the middleware;
and monitoring and auditing the storage condition and the consumption condition of the Socket encrypted message through the message monitor.
In one example, the monitoring and auditing, by the message monitor, the storage condition and the consumption condition of the Socket encrypted message specifically includes:
recording the storage condition and the consumption condition of the Socket encryption message when the storage condition and the consumption condition of the Socket encryption message are monitored through the message monitor, wherein the storage condition comprises the following steps: determining that the message receiver receives the Socket encryption message, determining that the message memory stores the Socket encryption message, and the consumption condition includes: determining that the message sender extracts the Socket encryption message, determining that the message sender sends the Socket encryption message, determining that the message sender receives the response, and determining that the message sender times out due to the fact that the response is not received.
In one example, the method further comprises:
and determining the corresponding severity level according to the monitored storage condition and consumption condition through the message monitor, and synchronously displaying the corresponding severity level when displaying the monitored storage condition and consumption condition to a user, wherein a plurality of severity levels are set for the storage condition or the consumption condition.
On the other hand, the application also provides data interaction equipment aiming at different architecture applications, which comprises:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform operations such as: the data interaction method for different architecture applications as described in any of the above examples.
In another aspect, the present application also provides a non-volatile computer storage medium storing computer-executable instructions configured to: the data interaction method for different architecture applications as described in any of the above examples.
The data interaction method aiming at different architecture applications can bring the following beneficial effects:
compared with the traditional registry protocol, the method and the device can complete the data interaction across the framework without changing the system registry. As the middleware, the browser internal page application and the local client application to be integrated are not coupled, the browser internal page application and the local client application to be interacted only need to send Socket encryption information to the middleware according to the agreed form of the middleware, the middleware does not sense the content of the information body and feed back corresponding Socket encryption information, and the receiving end can analyze and process the information according to the agreed form with the sending end after receiving the Socket encryption information, so that the data exchange safety is ensured.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
FIG. 1 is a flow chart of a method of data interaction for different architecture applications in an embodiment of the present application;
FIG. 2 is a schematic diagram of a framework composed of each end and middleware according to an embodiment of the present application;
FIG. 3 is a schematic diagram showing severity level synchronization in an embodiment of the present application;
fig. 4 is a schematic diagram of a data interaction method device for different architecture applications in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.
As shown in fig. 1, an embodiment of the present application provides a data interaction method for different architecture applications, including:
s101: and determining a plurality of applications and middleware, wherein the plurality of applications are arranged in the terminal, the plurality of applications at least comprise applications realized through different architectures, and the architectures comprise a C/S architecture and a B/S architecture.
As shown in fig. 2, the middleware may be provided in the local terminal and belong to the same terminal as the other applications. The C/S architecture refers to a Server-Client architecture, i.e., a Client-Server (C/S) architecture. The C/S architecture typically takes a two-layer structure. The server is responsible for data management and the client is responsible for completing the interaction tasks with the user. The B/S structure (Browser/Server) is a network structure mode after the WEB is raised, and the WEB Browser is the most main application software of the client.
S102: and receiving Socket encryption information sent by a sending end through the middleware, wherein the sending end belongs to an application in the plurality of applications, and the Socket encryption information is obtained by encrypting interaction information based on a contract form.
The sending end can be an application based on a C/S architecture or an application of a B/S architecture.
As shown in fig. 2, it is determined that the middleware includes a message parser. The definition of the message format and the meaning rule analysis are provided through the message analyzer, at this time, the sender and the receiver can analyze based on the definition of the message format and the meaning rule to generate a contract form, the message analyzer only provides the definition of the format and the meaning rule, and does not provide a specific contract form, and the contract form is custom-generated between the sender and the receiver, so that the finally obtained Socket encrypted message can only analyze between the sender and the receiver. The sending end encrypts the interaction message through the appointed form to obtain a Socket encryption message.
S103: storing the Socket encryption message, and forwarding the Socket encryption message to a receiving end, wherein the receiving end belongs to one of the applications and is realized by a different structure with the sending end.
As shown in fig. 2, the middleware includes a message receiver and a message memory. And receiving the Socket encrypted message through a message receiver and sending the Socket encrypted message to the message memory. And encrypting the Socket by the message memory, and continuously storing the classified queues according to the message header.
As shown in fig. 2, the middleware includes a message sender. The message sender is used for extracting the Socket encrypted message according to a first set frequency in the message memory, sending the extracted Socket encrypted message to the receiving end, returning the received feedback information by the receiving end after the Socket encrypted message is sent to the receiving end, providing message sending confirmation information by the middleware (for example, popping up a dialog box at a front end interface to display sent information or setting a corresponding sending list at the front end interface to display the sent information), providing a retry mechanism after the Socket encrypted message is not sent to the receiving end successfully, and sending the Socket encrypted message which is not sent successfully again after the user clicks retry.
Further, for high-frequency message interaction (high frequency refers to the frequency corresponding to the time when the message interaction times in the preset duration are higher than the preset times), message queue support is provided through the message memory, so that Socket encrypted messages are stored in the message queue, and the influence caused by the high-frequency interaction is prevented from spreading to a message sender and even spreading to a receiving end application system.
And extracting the Socket encrypted message according to a second set frequency (the second set frequency is faster than the first set frequency because of high-frequency message interaction at the moment) in the message memory by the message transmitter, and transmitting the extracted Socket encrypted message to the receiving end, so that faster message transmission is realized.
And after the Socket encrypted message is sent to the receiving end, providing message sending confirmation information, and after the Socket encrypted message is not successfully sent to the receiving end, providing a retry mechanism, wherein the corresponding retry times in the retry mechanism are configured based on a message header matching rule, for example, different message headers indicate the behavior of the message, so that the behavior of the message can be judged based on the message headers, thereby different retry times are formulated for different behaviors in advance, and the more important the behavior is, the more retry times are.
S104: and analyzing the Socket encryption message based on the appointed form through the receiving end so as to acquire the interaction message.
Because the agreed form is agreed between the receiving end and the sending end, the receiving end can analyze the Socket encryption message, thereby obtaining the interaction message.
Compared with the traditional registry protocol, the method and the device can complete the data interaction across the framework without changing the system registry. As the middleware, the browser internal page application and the local client application to be integrated are not coupled, the browser internal page application and the local client application to be interacted only need to send Socket encryption information to the middleware according to the agreed form of the middleware, the middleware does not sense the content of the information body and feed back corresponding Socket encryption information, and the receiving end can analyze and process the information according to the agreed form with the sending end after receiving the Socket encryption information, so that the data exchange safety is ensured.
In one embodiment, as shown in FIG. 2, the middleware includes a message monitor. And monitoring and auditing the storage condition and the consumption condition of the Socket encrypted message through the message monitor, so that the complete interaction process can be traced conveniently.
Specifically, when the storage condition and the consumption condition of the Socket encrypted message are monitored through the message monitor, the storage condition and the consumption condition are recorded, wherein the storage condition comprises the following steps: determining that the message receiver receives the Socket encryption message, determining that the message memory stores the Socket encryption message, and the consumption condition comprises: the method comprises the steps of determining that a message sender extracts a Socket encryption message, determining that the message sender sends a Socket encryption message, determining that the message sender receives a response, and determining that the message sender overtime due to the fact that the message sender does not receive the response.
Further, through the message monitor, the corresponding severity level is determined according to the monitored storage condition and consumption condition, and as shown in fig. 3, when the monitored storage condition and consumption condition are displayed to the user, the corresponding severity level is synchronously displayed, wherein a plurality of severity levels are set for the storage condition or the consumption condition. For example, two severity levels of "serious" and "normal" are set, corresponding to different storage conditions and consumption conditions respectively when different events occur. Of course, the content of the name, type, recording time, module, transmission source (corresponding to the transmitting end), receiving end (corresponding to the receiving end), operation details and the like of the interactive message can also be displayed to the user. And a screening module is provided so that a user can screen the content to be queried through the keywords or the drop-down menu.
As shown in fig. 4, an embodiment of the present application further provides a data interaction device for different architecture applications, including:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform operations such as: the data interaction method for different architecture applications according to any of the embodiments.
The embodiment of the application also provides a nonvolatile computer storage medium, which stores computer executable instructions, wherein the computer executable instructions are configured to: the data interaction method for different architecture applications according to any of the embodiments.
The embodiments of the present application are described in a progressive manner, and the same and similar parts of the embodiments are all referred to each other, and each embodiment is mainly described in the differences from the other embodiments. In particular, for the apparatus and medium embodiments, the description is relatively simple, as it is substantially similar to the method embodiments, with reference to the section of the method embodiments being relevant.
The devices and media provided in the embodiments of the present application are in one-to-one correspondence with the methods, so that the devices and media also have similar beneficial technical effects as the corresponding methods, and since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media are not repeated here.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
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 one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.

Claims (10)

1. A method of data interaction for different architecture applications, comprising:
determining a plurality of applications and middleware, wherein the plurality of applications are arranged in a terminal and at least comprise applications realized through different architectures, and the architectures comprise a C/S architecture and a B/S architecture;
receiving, by the middleware, a Socket encrypted message sent by a sending end, where the sending end belongs to an application in the plurality of applications, and the Socket encrypted message is obtained by encrypting an interaction message based on a contract form;
storing the Socket encryption message, and forwarding the Socket encryption message to a receiving end, wherein the receiving end belongs to one of the applications and is realized by a different structure with the sending end;
and analyzing the Socket encryption message based on the appointed form through the receiving end so as to acquire the interaction message.
2. The method according to claim 1, wherein before receiving, by the middleware, the Socket encrypted message sent by the sender, the method further comprises:
determining a message parser contained in the middleware;
and providing definition of the message format and meaning rule analysis by the message analyzer so as to generate a contracted form between the sending end and the receiving end based on the definition of the message format and the meaning rule analysis.
3. The method according to claim 1, wherein storing the Socket encrypted message specifically comprises:
determining a message receiver and a message memory contained in the middleware;
receiving the Socket encryption message through the message receiver, and sending the Socket encryption message to the message memory;
and encrypting the Socket information through the information memory, and continuously storing the classified queues according to the information head.
4. The method of claim 3, wherein forwarding the Socket encrypted message to a receiving end specifically includes:
determining a message sender contained in the middleware;
and extracting the Socket encrypted message according to a first set frequency in the message memory by the message transmitter, transmitting the extracted Socket encrypted message to a receiving end, providing message transmission confirmation information after the Socket encrypted message is transmitted to the receiving end, and providing a retry mechanism after the Socket encrypted message is not successfully transmitted to the receiving end.
5. The method according to claim 4, wherein the method further comprises:
providing message queue support through the message memory for high-frequency message interaction to store the Socket encrypted message into the message queue, wherein the high frequency refers to a frequency corresponding to the time when the message interaction times in the preset duration are higher than the preset times;
extracting Socket encryption information according to a second set frequency in the information memory by the information transmitter, and transmitting the extracted Socket encryption information to a receiving end, wherein the second set frequency is faster than the first set frequency;
and providing a retry mechanism after the Socket encrypted message is sent to the receiving end and after the Socket encrypted message is not successfully sent to the receiving end, wherein the corresponding retry times in the retry mechanism are configured based on a message header matching rule.
6. The method according to claim 4, wherein the method further comprises:
determining a message monitor contained in the middleware;
and monitoring and auditing the storage condition and the consumption condition of the Socket encrypted message through the message monitor.
7. The method according to claim 6, wherein monitoring and auditing the storage condition and consumption condition of the Socket encrypted message by the message monitor specifically comprises:
recording the storage condition and the consumption condition of the Socket encryption message when the storage condition and the consumption condition of the Socket encryption message are monitored through the message monitor, wherein the storage condition comprises the following steps: determining that the message receiver receives the Socket encryption message, determining that the message memory stores the Socket encryption message, and the consumption condition includes: determining that the message sender extracts the Socket encryption message, determining that the message sender sends the Socket encryption message, determining that the message sender receives the response, and determining that the message sender times out due to the fact that the response is not received.
8. The method of claim 7, wherein the method further comprises:
and determining the corresponding severity level according to the monitored storage condition and consumption condition through the message monitor, and synchronously displaying the corresponding severity level when displaying the monitored storage condition and consumption condition to a user, wherein a plurality of severity levels are set for the storage condition or the consumption condition.
9. A data interaction device for different architecture applications, comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform operations such as: a method of data interaction for different architectural applications as claimed in any of claims 1 to 8.
10. A non-transitory computer storage medium storing computer-executable instructions, the computer-executable instructions configured to: a method of data interaction for different architectural applications as claimed in any of claims 1 to 8.
CN202311111181.0A 2023-08-30 2023-08-30 Data interaction method, device and medium for different architecture applications Pending CN117061205A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311111181.0A CN117061205A (en) 2023-08-30 2023-08-30 Data interaction method, device and medium for different architecture applications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311111181.0A CN117061205A (en) 2023-08-30 2023-08-30 Data interaction method, device and medium for different architecture applications

Publications (1)

Publication Number Publication Date
CN117061205A true CN117061205A (en) 2023-11-14

Family

ID=88653483

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311111181.0A Pending CN117061205A (en) 2023-08-30 2023-08-30 Data interaction method, device and medium for different architecture applications

Country Status (1)

Country Link
CN (1) CN117061205A (en)

Similar Documents

Publication Publication Date Title
US10817324B2 (en) System and method of cross-silo discovery and mapping of storage, hypervisors and other network objects
US9934003B2 (en) System and method for creating a development and operational platform for mobile applications
US10362086B2 (en) Method and system for automating submission of issue reports
US20210400114A1 (en) Methods and apparatus for census and panel matching using http headers
CN110727560A (en) Cloud service alarm method and device
CN111913738A (en) Access request processing method, device, computing equipment and medium
US9154539B2 (en) Consolidating event data from different sources
CN110737639A (en) Audit log method, device, computer equipment and storage medium
CN105930249B (en) Using monitoring method and device
CN107295031A (en) A kind of method of data synchronization and device
CN111859205A (en) Analytic method and equipment for batch processing tasks
US10432490B2 (en) Monitoring single content page application transitions
EP3754998B1 (en) Streaming media quality monitoring method and system
CN113360413A (en) Code testing method and device
WO2015035086A1 (en) Systems and methods for deriving, storing, and visualizing a numeric baseline for time-series numeric data which considers the time, coincidental events, and relevance of the data points as part of the derivation and visualization
CN110297945B (en) Data information processing method and system based on XBRL
CN111324480A (en) Large host transaction fault positioning system and method
CN117061205A (en) Data interaction method, device and medium for different architecture applications
US20200192778A1 (en) Real-time collaboration dynamic logging level control
US20140337728A1 (en) Operating oracle forms using a web service
CN105554134A (en) Information synchronization and device
CN112671876B (en) Method and equipment for page operation and maintenance
CN112202598B (en) Log recording method and device
CN110908886A (en) Data sending method and device, electronic equipment and storage medium
CN114125054B (en) Content auditing system, 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