CN112383415A - Server side marking method and equipment - Google Patents
Server side marking method and equipment Download PDFInfo
- Publication number
- CN112383415A CN112383415A CN202011192766.6A CN202011192766A CN112383415A CN 112383415 A CN112383415 A CN 112383415A CN 202011192766 A CN202011192766 A CN 202011192766A CN 112383415 A CN112383415 A CN 112383415A
- Authority
- CN
- China
- Prior art keywords
- server
- request
- current
- mark
- current server
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
Abstract
The invention aims to provide a server marking method and equipment, and a 64-bit request mark, namely traceId, and a server mark, namely spanId are generated through a zipkin framework after a first server receives a request of a client. Subsequent servers in the current request will receive the last server traceId and then generate a new spanId. All the service terminals in one request share one request mark, namely traceId; each server generates a server id in a request. According to the method and the system, the request mark and the service mark generated by the server are used as the link mark, the link mark is added in the returned result, and when the client requests the server, the problem where the problem is located can be located through the returned link mark.
Description
Technical Field
The invention relates to the field of computers, in particular to a server side marking method and equipment.
Background
In the existing scheme, the problem that the request between the server and the client cannot be quickly positioned often occurs.
Disclosure of Invention
The invention aims to provide a server side marking method and equipment.
According to an aspect of the present invention, there is provided a server-side labeling method, including:
step S1, the first server side obtains the request sent by the client side;
step S2, the first server is taken as the current server;
step S3, the current server generates a request identifier corresponding to the request and a server identifier corresponding to the current server based on the request, stores the request identifier corresponding to the request and the server identifier corresponding to the current server in the current server, and sends the request identifier and the server identifier corresponding to the current server to the next server;
step S4, taking the next server as the current server, the current server generating the server mark corresponding to the current server based on the request mark received from the previous server and the server mark corresponding to the previous server, and storing the request mark and the server mark corresponding to the current server at the current server;
step S5, if the current server is the end server, the current server returns the request mark and the server mark corresponding to the current server to the client;
in step S6, if the current server is not the end server, the process is resumed from step S4.
Further, in the above method, in step S5, if the current server is the end server, and after the request identifier and the server identifier corresponding to the current server are returned to the client, the method further includes:
the client compares the received request mark and the service end mark with the request mark and the service end mark recorded in each service end to obtain the service end through which the request passes;
and locating the problematic server based on the content of the log of the server through which the request passes.
Further, in the above method, in step S3 or step S5, the sending, by the current server, the request identifier corresponding to the request and the server identifier corresponding to the current server to the next server or the client includes:
and the current server writes the request mark corresponding to the request and the server mark corresponding to the current server into a byte code file, and sends the byte code file to the next server or client.
Further, in the above method, in step S3 or S4, the generating, by the current server, the request identifier corresponding to the request and/or the server identifier corresponding to the current server includes:
and the current server generates a request mark corresponding to the request and/or a server mark corresponding to the current server through zipkin.
According to another aspect of the present invention, there is also provided a server-side labeling apparatus, wherein the apparatus includes:
the first device is used for the first server to obtain the request sent by the client;
the second device is used for taking the first server as the current server;
a third device, configured to enable the current server to generate a request identifier corresponding to the request and a server identifier corresponding to the current server based on the request, store the request identifier corresponding to the request and the server identifier corresponding to the current server at the current server, and send the request identifier and the server identifier corresponding to the current server to a next server;
a fourth device, configured to use a next service end as a current service end, where the current service end generates a service end identifier corresponding to the current service end based on a request identifier received from a previous service end and a service end identifier corresponding to the previous service end, and stores the request identifier and the service end identifier corresponding to the current service end in the current service end;
a fifth device, configured to, if the current server is an end server, return, by the current server, the request identifier and a server identifier corresponding to the current server to the client;
and a sixth means for restarting execution from the fourth means if the current server is not the end server.
Further, in the above apparatus, the fifth device is further configured to compare the received request identifier and service identifier with the request identifier and service identifier recorded in each service to obtain a service through which the request passes; and locating the problematic server based on the content of the log of the server through which the request passes.
Further, in the above apparatus, the third device is configured to enable the current server to write a request identifier corresponding to the request and a server identifier corresponding to the current server into a byte code file, and send the byte code file to a next server;
and the fifth device is used for writing the request mark corresponding to the request and the server mark corresponding to the current server into a byte code file by the current server and sending the byte code file to the client.
Further, in the above apparatus, the third device is configured to generate, by the current server, a request identifier corresponding to the request and a server identifier corresponding to the current server through zipkin;
and the fifth device is used for generating a server mark corresponding to the current server by the current server through zipkin.
According to another aspect of the present invention, there is also provided a computer readable medium having computer readable instructions stored thereon, the computer readable instructions being executable by a processor to implement the method of any one of the above.
According to another aspect of the present invention, there is also provided an apparatus for information processing at a network device, the apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform any of the methods described above.
Compared with the prior art, the method generates 64-bit request mark, namely traceId, and the service mark, namely spanId, through a zipkin framework after the first service end receives the request of the client. Subsequent servers in the current request will receive the last server traceId and then generate a new spanId. All the service terminals in one request share one request mark, namely traceId; each server generates a server id in a request. According to the method and the system, the request mark and the service mark generated by the server are used as the link mark, the link mark is added in the returned result, and when the client requests the server, the problem where the problem is located can be located through the returned link mark.
Drawings
Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings:
fig. 1 is a schematic diagram illustrating a service-side marking method according to an embodiment of the present invention.
The same or similar reference numbers in the drawings identify the same or similar elements.
Detailed Description
The present invention is described in further detail below with reference to the attached drawing figures.
In a typical configuration of the present application, the terminal, the device serving the network, and the trusted party each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
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 computer storage media 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 that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
As shown in fig. 1, the present invention provides a method for identifying a server, where the method includes:
step S1, the first server side obtains the request sent by the client side;
here, the client refers to a request initiated in a front end, i.e., a browser;
step S2, the first server is taken as the current server;
step S3, the current server generates a request identifier corresponding to the request and a server identifier corresponding to the current server based on the request, stores the request identifier corresponding to the request and the server identifier corresponding to the current server in the current server, and sends the request identifier and the server identifier corresponding to the current server to the next server;
here, the server side marks are spanids, and when a request is initiated from the client side to the server side, each server side can generate a 64-bit ID unique identifier spanId;
the request mark is traceId, when a request is initiated from a client to a server, the traceId is generated only at the initial server, and the servers which are subsequently passed by the current request are the same traceId;
step S4, taking the next server as the current server, the current server generating the server mark corresponding to the current server based on the request mark received from the previous server and the server mark corresponding to the previous server, and storing the request mark and the server mark corresponding to the current server at the current server;
step S5, if the current server is the end server, the current server returns the request mark and the server mark corresponding to the current server to the client;
in step S6, if the current server is not the end server, the process is resumed from step S4.
Here, after receiving the request of the client, the first server generates a 64-bit request identifier, i.e., traceId, and a server identifier, i.e., spanId, through a zipkin framework. Subsequent servers in the current request will receive the last server traceId and then generate a new spanId. All the service terminals in one request share one request mark, namely traceId; each server generates a server id in a request. According to the method and the system, the request mark and the service mark generated by the server are used as the link mark, the link mark is added in the returned result, and when the client requests the server, the problem where the problem is located can be located through the returned link mark.
In an embodiment of the method for marking a server side of the present invention, in step S5, if the current server side is the end server side, after returning the request mark and the server side mark corresponding to the current server side to the client side, the method further includes:
the client compares the received request mark and the service end mark with the request mark and the service end mark recorded in each service end to obtain the service end through which the request passes;
and locating the problematic server based on the content of the log of the server through which the request passes.
The traceId (full link identifier) and the spanId (link basic unit) generated by the server are returned to the client, so that the client can obtain the traceId and the spanId, and when a certain server has a problem, the server with the problem can be known through the returned traceId and the spanId.
In an embodiment of the method for marking a server of a client, in step S3 or step S5, the method for sending, by a current server, a request mark corresponding to the request and a server mark corresponding to the current server to a next server or client includes:
and the current server writes the request mark corresponding to the request and the server mark corresponding to the current server into a byte code file, and sends the byte code file to the next server or client.
Here, the link label generated by the server is returned to the client through java byte code enhancement technology.
When a client initiates a request to a server, the server returns a result to the client, in the process, a java byte code (. class file) of the returned result is modified, a traceId (full link identifier) and a span id (link basic unit) are written into the byte code (. class file), then a new byte code (. class file) is generated, and the client acquires the traceId (full link identifier) and the span id (link basic unit) in the new byte code, so that the client can know which servers the request of the client passes through, and the problematic server can be quickly positioned.
Java can be compiled once and run everywhere, because JVM is customized for various operating systems and platforms, and because whatever platform is, it can be compiled to generate fixed format bytecode (. class file) for use by JVM. Bytecode is called because the bytecode file is composed of hexadecimal values, and the JVM reads in groups of two hexadecimal values, i.e., in units of bytes.
Read the compiled bytecode (. class file) and modify the content to achieve the desired effect, and then generate a new bytecode (. class file) for use by the JVM.
Modifying the compiled bytecode (. class file) when returning the result to the client, writing the traceId (full link identification) and the span Id (link basic unit) generated by the server into the bytecode (. class file), so that the client can obtain the traceId and the span Id, and knowing the server with the problem through the returned traceId and the span Id when the server has the problem.
In an embodiment of the method for marking a server of the present invention, in step S3 or S4, the step of generating, by the current server, a request mark corresponding to the request and/or a server mark corresponding to the current server includes:
and the current server generates a request mark corresponding to the request and/or a server mark corresponding to the current server through zipkin.
The method and the system realize the problem of quick positioning of the problem of the request between the client and the server based on the zipkin and java byte code enhancement.
The role of zipkin is in the whole receiving and initiating process of the server, and the traceId and the spanId are generated in the process of receiving the request of the client, which is the process of the server 1 in the figure.
Zipkin passes the traceId through when the server 1 makes a request to the server 2.
When the server 2 receives the request of the server 1, it finds that the traceId is carried, and then a new traceId is not generated, and only a new spanId is generated.
When the server 2 returns the result to the client, the returned result bytecode file is modified through bytecode enhancement, and the traceId and span2 generated by the server 1 are written into the returned result bytecode file, so that the client can obtain the link identification.
According to another aspect of the present invention, there is also provided a server-side labeling apparatus, wherein the apparatus includes:
the first device is used for the first server to obtain the request sent by the client;
the second device is used for taking the first server as the current server;
a third device, configured to enable the current server to generate a request identifier corresponding to the request and a server identifier corresponding to the current server based on the request, store the request identifier corresponding to the request and the server identifier corresponding to the current server at the current server, and send the request identifier and the server identifier corresponding to the current server to a next server;
a fourth device, configured to use a next service end as a current service end, where the current service end generates a service end identifier corresponding to the current service end based on a request identifier received from a previous service end and a service end identifier corresponding to the previous service end, and stores the request identifier and the service end identifier corresponding to the current service end in the current service end;
a fifth device, configured to, if the current server is an end server, return, by the current server, the request identifier and a server identifier corresponding to the current server to the client;
and a sixth means for restarting execution from the fourth means if the current server is not the end server.
Further, in the above apparatus, the fifth device is further configured to compare the received request identifier and service identifier with the request identifier and service identifier recorded in each service to obtain a service through which the request passes; and locating the problematic server based on the content of the log of the server through which the request passes.
Further, in the above apparatus, the third device is configured to enable the current server to write a request identifier corresponding to the request and a server identifier corresponding to the current server into a byte code file, and send the byte code file to a next server;
and the fifth device is used for writing the request mark corresponding to the request and the server mark corresponding to the current server into a byte code file by the current server and sending the byte code file to the client.
Further, in the above apparatus, the third device is configured to generate, by the current server, a request identifier corresponding to the request and a server identifier corresponding to the current server through zipkin;
and the fifth device is used for generating a server mark corresponding to the current server by the current server through zipkin.
According to another aspect of the present invention, there is also provided a computer readable medium having computer readable instructions stored thereon, the computer readable instructions being executable by a processor to implement the method of any one of the above.
According to another aspect of the present invention, there is also provided an apparatus for information processing at a network device, the apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform any of the methods described above.
For details of embodiments of each device and storage medium of the present invention, reference may be made to corresponding parts of each method embodiment, and details are not described herein again.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
It should be noted that the present invention may be implemented in software and/or in a combination of software and hardware, for example, as an Application Specific Integrated Circuit (ASIC), a general purpose computer or any other similar hardware device. In one embodiment, the software program of the present invention may be executed by a processor to implement the steps or functions described above. Also, the software programs (including associated data structures) of the present invention can be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Further, some of the steps or functions of the present invention may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
In addition, some of the present invention can be applied as a computer program product, such as computer program instructions, which when executed by a computer, can invoke or provide the method and/or technical solution according to the present invention through the operation of the computer. Program instructions which invoke the methods of the present invention may be stored on a fixed or removable recording medium and/or transmitted via a data stream on a broadcast or other signal-bearing medium and/or stored within a working memory of a computer device operating in accordance with the program instructions. An embodiment according to the invention herein comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or solution according to embodiments of the invention as described above.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.
Claims (10)
1. A method for marking a server side comprises the following steps:
step S1, the first server side obtains the request sent by the client side;
step S2, the first server is taken as the current server;
step S3, the current server generates a request identifier corresponding to the request and a server identifier corresponding to the current server based on the request, stores the request identifier corresponding to the request and the server identifier corresponding to the current server in the current server, and sends the request identifier and the server identifier corresponding to the current server to the next server;
step S4, taking the next server as the current server, the current server generating the server mark corresponding to the current server based on the request mark received from the previous server and the server mark corresponding to the previous server, and storing the request mark and the server mark corresponding to the current server at the current server;
step S5, if the current server is the end server, the current server returns the request mark and the server mark corresponding to the current server to the client;
in step S6, if the current server is not the end server, the process is resumed from step S4.
2. The method according to claim 1, wherein, in step S5, after returning the request flag and the server flag corresponding to the current server to the client if the current server is the end server, the method further includes:
the client compares the received request mark and the service end mark with the request mark and the service end mark recorded in each service end to obtain the service end through which the request passes;
and locating the problematic server based on the content of the log of the server through which the request passes.
3. The method of claim 1, wherein in step S3 or step S5, the step of sending, by the current server, the request tag corresponding to the request and the server tag corresponding to the current server to a next server or client comprises:
and the current server writes the request mark corresponding to the request and the server mark corresponding to the current server into a byte code file, and sends the byte code file to the next server or client.
4. The method as claimed in claim 1, wherein in step S3 or S4, the step of generating, by the current server, a request flag corresponding to the request and/or a server flag corresponding to the current server includes:
and the current server generates a request mark corresponding to the request and/or a server mark corresponding to the current server through zipkin.
5. A server side signage apparatus, wherein the apparatus comprises:
the first device is used for the first server to obtain the request sent by the client;
the second device is used for taking the first server as the current server;
a third device, configured to enable the current server to generate a request identifier corresponding to the request and a server identifier corresponding to the current server based on the request, store the request identifier corresponding to the request and the server identifier corresponding to the current server at the current server, and send the request identifier and the server identifier corresponding to the current server to a next server;
a fourth device, configured to use a next service end as a current service end, where the current service end generates a service end identifier corresponding to the current service end based on a request identifier received from a previous service end and a service end identifier corresponding to the previous service end, and stores the request identifier and the service end identifier corresponding to the current service end in the current service end;
a fifth device, configured to, if the current server is an end server, return, by the current server, the request identifier and a server identifier corresponding to the current server to the client;
and a sixth means for restarting execution from the fourth means if the current server is not the end server.
6. The apparatus according to claim 5, wherein the fifth means is further configured to compare the received request identifier and service identifier with the request identifier and service identifier recorded in each service to obtain a service through which the request passes; and locating the problematic server based on the content of the log of the server through which the request passes.
7. The apparatus according to claim 5, wherein the third means is configured to write, by the current server, a request identifier corresponding to the request and a server identifier corresponding to the current server into a bytecode file, and send the bytecode file to a next server;
and the fifth device is used for writing the request mark corresponding to the request and the server mark corresponding to the current server into a byte code file by the current server and sending the byte code file to the client.
8. The apparatus according to claim 5, wherein the third means is configured to generate, by a current server, a request identifier corresponding to the request and a server identifier corresponding to the current server through zipkin;
and the fifth device is used for generating a server mark corresponding to the current server by the current server through zipkin.
9. A computer readable medium having computer readable instructions stored thereon which are executable by a processor to implement the method of any one of claims 1 to 4.
10. An apparatus for information processing at a network device, the apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform the method of any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011192766.6A CN112383415A (en) | 2020-10-30 | 2020-10-30 | Server side marking method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011192766.6A CN112383415A (en) | 2020-10-30 | 2020-10-30 | Server side marking method and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112383415A true CN112383415A (en) | 2021-02-19 |
Family
ID=74576883
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011192766.6A Pending CN112383415A (en) | 2020-10-30 | 2020-10-30 | Server side marking method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112383415A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012139328A1 (en) * | 2011-04-14 | 2012-10-18 | 中兴通讯股份有限公司 | Cache server system and application method thereof, cache client, and cache server |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN108173915A (en) * | 2017-12-21 | 2018-06-15 | 中国联合网络通信集团有限公司 | Call chain processing method and processing device |
| CN110535722A (en) * | 2019-08-27 | 2019-12-03 | 江苏瑞中数据股份有限公司 | A kind of full link operation and monitoring method of the micro services in cross-safety zone domain |
-
2020
- 2020-10-30 CN CN202011192766.6A patent/CN112383415A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012139328A1 (en) * | 2011-04-14 | 2012-10-18 | 中兴通讯股份有限公司 | Cache server system and application method thereof, cache client, and cache server |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN108173915A (en) * | 2017-12-21 | 2018-06-15 | 中国联合网络通信集团有限公司 | Call chain processing method and processing device |
| CN110535722A (en) * | 2019-08-27 | 2019-12-03 | 江苏瑞中数据股份有限公司 | A kind of full link operation and monitoring method of the micro services in cross-safety zone domain |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107122296B (en) | Method and apparatus for data assertion for test interface | |
| US20170272499A1 (en) | Method and device for loading webpage | |
| CN108512726B (en) | Data monitoring method and equipment | |
| CN110362547B (en) | Method and device for encoding, analyzing and storing log file | |
| CN109144625B (en) | Anti-duplicate submission method, device and system | |
| WO2017107808A1 (en) | Method and system for locating obfuscated scripting language | |
| CN112667246A (en) | Application function extension method and device and electronic equipment | |
| CN111314535A (en) | Method and equipment for recording quality inspection process of mobile phone | |
| CN115470156A (en) | RDMA-based memory use method, system, electronic device and storage medium | |
| CN106874173B (en) | Page template testing method and device | |
| CN112860661B (en) | Method and device for generating data sequence identification | |
| CN108268369B (en) | Test data acquisition method and device | |
| CN112860507A (en) | Method and device for controlling sampling rate of distributed link tracking system | |
| CN112383415A (en) | Server side marking method and equipment | |
| CN109977317B (en) | Data query method and device | |
| CN112256984A (en) | Method and device for acquiring interface background screenshot corresponding to webpage | |
| CN103473106A (en) | Method and system for generating page | |
| CN111464598A (en) | Data pushing method and device | |
| CN110321505A (en) | Data consistency verification method and device | |
| CN110929188A (en) | Method and device for rendering server page | |
| CN114510300A (en) | Method and equipment for embedding target object in derived class | |
| CN114064111A (en) | Management method and equipment for version information of deployment package | |
| CN112069519A (en) | Method and equipment for outputting encrypted record of information file | |
| CN112632211A (en) | Semantic information processing method and equipment for mobile robot | |
| US10853057B1 (en) | Software library versioning with caching |
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 |