CN106055383A - Request processing method and device - Google Patents
Request processing method and device Download PDFInfo
- Publication number
- CN106055383A CN106055383A CN201610362332.3A CN201610362332A CN106055383A CN 106055383 A CN106055383 A CN 106055383A CN 201610362332 A CN201610362332 A CN 201610362332A CN 106055383 A CN106055383 A CN 106055383A
- Authority
- CN
- China
- Prior art keywords
- request
- route
- result
- contract
- files
- 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
- 238000003672 processing method Methods 0.000 title abstract description 16
- 238000004458 analytical method Methods 0.000 claims abstract description 31
- 238000000034 method Methods 0.000 claims abstract description 25
- 238000012545 processing Methods 0.000 claims abstract description 13
- 230000004044 response Effects 0.000 claims description 11
- 238000012546 transfer Methods 0.000 claims description 5
- 238000004088 simulation Methods 0.000 abstract description 31
- 238000010586 diagram Methods 0.000 description 11
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- OLDXRTOEUPVZKB-UHFFFAOYSA-N B1CCCC1 Chemical compound B1CCCC1 OLDXRTOEUPVZKB-UHFFFAOYSA-N 0.000 description 1
- 210000001072 colon Anatomy 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45529—Embedded in an application, e.g. JavaScript in a Web browser
-
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45508—Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a request processing method and device. The concrete embodiment of the method comprises following steps: receiving a request sent by a front end; analyzing the request and making matching analyses of an analyzing result and a pre-defined route; and returning a request result according to a matching analysis result to the front end. The embodiment is capable of processing the request of a simulation server to the front end.
Description
Technical Field
The present application relates to the field of computer technologies, in particular, to the field of internet technologies, and in particular, to a request processing method and apparatus.
Background
In the Web development of an actual project, with the function of a front-end framework being more and more perfect, the front-end and back-end separated development is a big trend, and the front-end and back-end can be developed in parallel after being separated. In the prior art, a simulation server (e.g., mock server system) may be built to simulate a back-end service interface to return data for a request sent by a front-end system, and a front-end contract and a back-end contract need to be agreed when the simulation server is built, for example, some codes may be written for each request of the front end to return corresponding simulation data, or a JSON (JavaScript Object Notation) file may be returned for each request.
Disclosure of Invention
It is an object of the present application to provide an improved request processing method and apparatus to solve the technical problems mentioned in the background section above.
In a first aspect, the present application provides a request processing method, including: receiving a request sent by a front end; analyzing the request, and performing matching analysis on an analysis result and a predefined route; and returning a request result to the front end according to the matching analysis result.
In some embodiments, before receiving the request sent by the front end, the method further comprises: reading a front-end and back-end contract file, wherein the front-end and back-end contract file comprises at least one requested route; and analyzing the route requested in the front-end and back-end contract files, and establishing the association between the route and the returned result.
In some embodiments, the returning the request result to the front end according to the matching analysis result includes: if the path and the parameters included in the request sent by the front end are matched with the predefined route, returning a return result associated with the route; if the path and the parameters included in the request sent by the front end do not match with the predefined route, a pre-agreed error response is returned.
In some embodiments, the front-back end contract file comprises at least one of: basic information nodes, routing nodes, error information nodes and public nodes; the basic information node comprises basic information of the front-end and back-end contract files; the routing node comprises a requested route and a return result of the route; the error node contains an intrinsic variable.
In some embodiments, the front-end and back-end contract files are JSON files.
In some embodiments, the request is a restful request or a hypertext transfer protocol HTTP request.
In a second aspect, the present application provides a request processing apparatus, the apparatus comprising: the receiving unit is used for receiving a request sent by the front end; the analysis unit is used for analyzing the request and performing matching analysis on an analysis result and a predefined route; and the return unit is used for returning the request result to the front end according to the matching analysis result.
In some embodiments, the apparatus further comprises: a reading unit, configured to read a front-end and back-end contract file, where the front-end and back-end contract file includes at least one requested route; and the establishing unit is used for analyzing the route requested in the front-end and back-end contract files and establishing the association between the route and the return result.
In some embodiments, the return unit is further configured to: if the path and the parameters included in the request sent by the front end are matched with the predefined route, returning a return result associated with the route; if the path and the parameters included in the request sent by the front end do not match with the predefined route, a pre-agreed error response is returned.
In some embodiments, the front-back end contract file comprises at least one of: basic information nodes, routing nodes, error information nodes and public nodes; the basic information node comprises basic information of the front-end and back-end contract files; the routing node comprises a requested route and a return result of the route; the error node contains an intrinsic variable.
In some embodiments, the front-end and back-end contract files are JSON files.
In some embodiments, the request is a restful request or a hypertext transfer protocol HTTP request.
According to the request processing method and device, the pre-established simulation server is used for analyzing the request sent by the front end, the analysis result is matched and analyzed with the plurality of routes which are defined in advance, and then the simulation server returns the request result to the front end according to the matching and analyzing result, so that the front end request is processed by the simulation server.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow diagram for one embodiment of a request processing method according to the present application;
FIG. 3 is a schematic diagram of an application scenario of a request processing method according to the present application;
FIG. 4 is a schematic block diagram of one embodiment of a request processing device according to the present application;
FIG. 5 is a schematic block diagram of a client computer system suitable for use in implementing embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the request processing method or request processing apparatus of the present application may be applied.
As shown in fig. 1, the system architecture 100 may include clients 101, 102, 103, a network 104, and a simulation server 105. Network 104 is the medium used to provide communication links between clients 101, 102, 103 and simulation server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
Developers can interact with the simulation server 105 through the front-end system on the clients 101, 102, 103 through the network 104 to send data requests and receive data, and to expose the received data. The front-end system may include a front-end interface of the developed system.
The clients 101, 102, 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts group Audio Layer III, motion Picture Experts compression standard Audio Layer 3), MP4 players (Moving Picture Experts group Audio Layer IV, motion Picture Experts compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like.
The simulation server 105 may be a simulation device capable of providing a back-end service interface for a front-end system, and may be obtained by building a mock server system.
It should be noted that the request processing method provided in the embodiment of the present application is generally executed by the simulation server 105, and accordingly, the request processing apparatus is generally disposed in the simulation server 105.
It should be understood that the number of clients, networks, and simulation servers in FIG. 1 are merely illustrative. There may be any number of clients, networks, and simulation servers, as desired for the implementation.
With continued reference to FIG. 2, a flow 200 of one embodiment of a request processing method according to the present application is shown. The request processing method comprises the following steps:
step 201, a request sent by a front end is received.
In this embodiment, the simulation device (for example, the simulation server 105 shown in fig. 1) on which the request processing method operates may receive the request sent by the front end in a wired connection manner or a wireless connection manner, where the request may include: request mode (including get, post, delete, put, etc.), type of response parameter to be returned, request parameter and parameter value, and URI (Uniform Resource Identifier) address, etc. The front end can be a foreground interface of a system developed by a Web developer, and can be used for data combination and page display. The simulation device may not be a real device, for example, the simulation server may be obtained by building a mock server system, and the simulation device may simulate a back-end environment to provide a service interface for a front-end, and may process and return a request of the front-end. It should be noted that the wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a uwb (ultra wideband) connection, and other wireless connection means now known or developed in the future.
In some optional implementations of this embodiment, the request may be a restful request manner or an HTTP request manner.
Step 202, parsing the request, and performing matching analysis on the parsed result and the predefined route.
In this embodiment, the simulation device may parse the request received in step 201, for example, a request manner of parsing the request from the request, a type of response parameter to be returned, a request parameter and a parameter value, and a URI address. And then, matching the analysis result with a predefined route, wherein the simulation equipment can predefine a plurality of routes during construction, each route can correspond to a request link address, and the simulation equipment can predefine the association between each route and the return result during construction.
And step 203, returning a request result to the front end according to the matching analysis result.
In this embodiment, according to the matching analysis result in step 202, the simulation device may return a request result to the front end, and the front end displays the returned request result.
In some optional implementation manners of this embodiment, before receiving the request sent by the front end, the request processing method further includes: the simulation device may read a front-end and back-end contract file, where the front-end and back-end contract file includes at least one requested route. The front-end and back-end contract files may be generated by the front-end developer and the back-end developer according to actual development requirements, for example, the front-end developer and the back-end developer may agree on which requests the developed website or Web application can respond to, the route of each request, what request parameters are, what organization mode of results returned by the request is, and the like. Then, the simulation device may analyze the route requested in the front-end and back-end contract file, establish a correlation between the route and the returned result, and complete the definition of the route.
In some optional implementations, the returning the request result to the front end according to the matching analysis result includes: if the path and the parameters included in the request sent by the front end are matched with the predefined route, returning a return result associated with the matched route; if the path and the parameters included in the request sent by the front end do not match with the predefined route, a pre-agreed error response is returned.
In some optional implementations, the front-back end contract file includes at least one of: basic information nodes, routing nodes, error information nodes and public nodes; wherein, the basic information node comprises the basic information of the front-end and back-end contract files; the routing node comprises a requested route and a return result of the route; the error node includes an inherent variable, and when the path and the parameter included in the request do not match the predefined route, the simulation device may return the inherent variable included in the error node to the front end, where the inherent variable is the predetermined error response.
Optionally, the front-end and back-end contract files may be JSON files, where the JSON files refer to files in a JSON format, where JSON (JavaScript Object notification) is a lightweight data exchange format, and the writing format of JSON data is: name/value pairs. Names in the name/value pair combination are written before (in the double quote) and value pairs are written after (also in the double quote), with the middle separated by a colon. As an example, a front-end and back-end contract file in JSON format is given below for explaining the format of the front-end and back-end contract file, specifically:
in the above example, the front-end and back-end contract file includes a basic information node, a routing node, and an error information node of the contract, and in addition, the front-end and back-end may further include one or more common nodes, a node name of the common node and an implemented function may be set according to actual needs, and the common node may be referred by other nodes, and may be implemented by using a # node name when referred.
Basic information of the front-back end contract file, such as name (name), description (desc), and the like, may be included in the basic information node (e.g., info node in the example); the routing node (e.g., route node in the example) may include a list of all routing nodes that the front-end and back-end contract files need to process, each routing node includes three child nodes, i.e., heads, parameters (params), and responses (responses), the routing node can process various HTTP request methods for a single route, e.g., get method, post method, put method, delete method, etc., and the parameters may include conventions for each parameter, e.g., name (name), whether it is necessary (request, false), type (type, e.g., integer, string, long, borolan, etc.), description of desc field, and so on. Here, various references can be made to the returned result, for example, # url: http:// xxxx can mean reading a remote file, # file: xxxx can mean reading a local file, and # variable name can mean reading a common node in a front-back contract file; when the path and the parameters included in the request are not matched with the route in the front-end and back-end contract files successfully, the returned result content can be read from the error information node, the error information node contains a fixed variable # error _ msg, and the final output result of the fixed variable can be that the XX field is not checked.
The above examples are merely illustrative of the format of the front and back end contract files, and are not intended to limit the front and back end contract files themselves, and the front and back end contract files may be set according to actual development requirements in actual use.
With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the request processing method according to the present embodiment. In the application scenario of fig. 3, the front end 301 first sends a data request to the simulation server 302; then, the simulation server 302 analyzes the received data request and matches the analysis result with a predefined route; finally, the request result corresponding to the route successfully matched is returned to the front end 301.
According to the method provided by the embodiment of the application, various requests of the front end are processed through the built simulation server, so that the front end and the rear end are efficiently and flexibly separated and developed
With further reference to fig. 4, as an implementation of the method shown in fig. 2, the present application provides an embodiment of a request processing apparatus, which may be applied in various electronic devices.
As shown in fig. 4, the request processing apparatus 400 according to the present embodiment includes: receiving section 401, parsing section 402, and returning section 403. The receiving unit 401 is configured to receive a request sent by a front end; the analyzing unit 402 is configured to analyze the request, and perform matching analysis on an analysis result and a predefined route; the returning unit 403 is configured to return a request result to the front end according to the matching analysis result.
In this embodiment, the detailed descriptions of step 201, step 202, and step 203 in the embodiment of fig. 2 may be referred to for the specific processing of the receiving unit 401, the parsing unit 402, and the returning unit 403, and are not repeated herein.
In some optional implementations of this embodiment, the apparatus further includes: a reading unit (not shown) for reading a front-end and back-end contract file, wherein the front-end and back-end contract file comprises at least one requested route; and an establishing unit (not shown) configured to parse the route requested in the front-end and back-end contract file, and establish an association between the route and the returned result. For the implementation, reference may be made to the detailed description of the corresponding implementation in the embodiment corresponding to fig. 2, which is not described herein again.
In some optional implementations of this embodiment, the returning unit 403 is further configured to: if the path and the parameters included in the request sent by the front end are matched with the predefined route, returning a return result associated with the route; if the path and the parameters included in the request sent by the front end do not match with the predefined route, a pre-agreed error response is returned. For the implementation, reference may be made to the detailed description of the corresponding implementation in the embodiment corresponding to fig. 2, which is not described herein again.
In some optional implementations of this embodiment, the front-end and back-end contract file includes at least one of: basic information nodes, routing nodes, error information nodes and public nodes; the basic information node comprises basic information of the front-end and back-end contract files; the routing node comprises a requested route and a return result of the route; the error node contains an intrinsic variable. For the implementation, reference may be made to the detailed description of the corresponding implementation in the embodiment corresponding to fig. 2, which is not described herein again.
In some optional implementations of this embodiment, the front-end and back-end contract files are JSON files. For the implementation, reference may be made to the detailed description of the corresponding implementation in the embodiment corresponding to fig. 2, which is not described herein again.
In some optional implementations of this embodiment, the request is a restful request manner or a hypertext transfer protocol HTTP request manner. For the implementation, reference may be made to the detailed description of the corresponding implementation in the embodiment corresponding to fig. 2, which is not described herein again.
Referring now to FIG. 5, shown is a block diagram of a computer system 500 suitable for use in implementing a client of an embodiment of the present application.
As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU)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. In the RAM 503, various programs and data necessary for the operation of the system 500 are also stored. The CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are 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.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-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 performs the above-described functions defined in the method of the present application when executed by the Central Processing Unit (CPU) 501.
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 application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a receiving unit, a parsing unit, and a returning unit. Where the names of these units do not in some cases constitute a limitation of the unit itself, for example, a receiving unit may also be described as a "unit that receives a request sent by a front end".
As another aspect, the present application also provides a non-volatile computer storage medium, which may be the non-volatile computer storage medium included in the apparatus in the above-described embodiments; or it may be a non-volatile computer storage medium that exists separately and is not incorporated into the terminal. The non-transitory computer storage medium stores one or more programs that, when executed by a device, cause the device to: receiving a request sent by a front end; analyzing the request, and performing matching analysis on an analysis result and a predefined route; and returning a request result to the front end according to the matching analysis result.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by a person skilled in the art that the scope of the invention as referred to in the present application is not limited to the embodiments with a specific combination of the above-mentioned features, but also covers other embodiments with any combination of the above-mentioned features or their equivalents without departing from the inventive concept. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (12)
1. A method for processing a request, the method comprising:
receiving a request sent by a front end;
analyzing the request, and performing matching analysis on an analysis result and a predefined route;
and returning a request result to the front end according to the matching analysis result.
2. The method of claim 1, wherein prior to receiving the request sent by the front end, the method further comprises:
reading a front-end and back-end contract file, wherein the front-end and back-end contract file comprises at least one requested route;
and analyzing the route requested in the front-end and back-end contract files, and establishing the association between the route and the returned result.
3. The method of claim 2, wherein returning the request result to the front end based on the matching analysis result comprises:
if the path and the parameters included in the request sent by the front end are matched with the predefined route, returning a return result associated with the route;
if the path and the parameters included in the request sent by the front end do not match with the predefined route, a pre-agreed error response is returned.
4. The method of claim 2, wherein the front-end contract file comprises at least one of:
basic information nodes, routing nodes, error information nodes and public nodes; wherein,
the basic information node comprises basic information of the front-end and back-end contract files;
the routing node comprises a requested route and a return result of the route;
the error node contains an intrinsic variable.
5. The method according to one of claims 2 to 4, wherein the front-end and back-end contract files are JSON files.
6. Method according to one of claims 1 to 4, characterized in that the request is a RESTful request mode or a hypertext transfer protocol HTTP request mode.
7. A request processing apparatus, characterized in that the apparatus comprises:
the receiving unit is used for receiving a request sent by the front end;
the analysis unit is used for analyzing the request and performing matching analysis on an analysis result and a predefined route;
and the return unit is used for returning the request result to the front end according to the matching analysis result.
8. The apparatus of claim 7, further comprising:
a reading unit, configured to read a front-end and back-end contract file, where the front-end and back-end contract file includes at least one requested route;
and the establishing unit is used for analyzing the route requested in the front-end and back-end contract files and establishing the association between the route and the return result.
9. The apparatus of claim 8, wherein the return unit is further configured to:
if the path and the parameters included in the request sent by the front end are matched with the predefined route, returning a return result associated with the route;
if the path and the parameters included in the request sent by the front end do not match with the predefined route, a pre-agreed error response is returned.
10. The apparatus of claim 8, wherein the front-end contract file comprises at least one of:
basic information nodes, routing nodes, error information nodes and public nodes; wherein,
the basic information node comprises basic information of the front-end and back-end contract files;
the routing node comprises a requested route and a return result of the route;
the error node contains an intrinsic variable.
11. The apparatus according to one of claims 8-10, wherein the front-end and back-end contract files are JSON files.
12. The apparatus according to one of claims 7-10, wherein the request is a restful request or a hypertext transfer protocol, HTTP, request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610362332.3A CN106055383A (en) | 2016-05-26 | 2016-05-26 | Request processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610362332.3A CN106055383A (en) | 2016-05-26 | 2016-05-26 | Request processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106055383A true CN106055383A (en) | 2016-10-26 |
Family
ID=57174864
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610362332.3A Pending CN106055383A (en) | 2016-05-26 | 2016-05-26 | Request processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106055383A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106598575A (en) * | 2016-11-30 | 2017-04-26 | 武汉斗鱼网络科技有限公司 | Front-end data simulation implementation method and system |
| CN106681922A (en) * | 2016-12-27 | 2017-05-17 | 广州唯品会信息科技有限公司 | Simulation server response method and system |
| CN108259520A (en) * | 2016-12-27 | 2018-07-06 | 北京国双科技有限公司 | A kind of data processing method and server |
| CN108268570A (en) * | 2017-01-04 | 2018-07-10 | 武汉斗鱼网络科技有限公司 | A kind of method and device of development interface |
| CN108600311A (en) * | 2018-03-21 | 2018-09-28 | 浙江口碑网络技术有限公司 | The method and device of client simulation interface data |
| CN109271310A (en) * | 2017-07-18 | 2019-01-25 | 北京京东尚科信息技术有限公司 | The exploitation test method and device of mobile applications network function |
| CN109388425A (en) * | 2018-08-17 | 2019-02-26 | 东莞数汇大数据有限公司 | A kind of interface switching method, system, device and the storage medium of front end engineering |
| CN109768951A (en) * | 2018-08-17 | 2019-05-17 | 付东光 | Remote analog data method and remote dummy server |
| CN109788010A (en) * | 2017-11-13 | 2019-05-21 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of data localization access |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102945078A (en) * | 2012-11-13 | 2013-02-27 | 深圳先进技术研究院 | Human-computer interaction equipment and human-computer interaction method |
| CN103686852A (en) * | 2012-09-07 | 2014-03-26 | 中国移动通信集团贵州有限公司 | Method, device and wireless acceleration system for processing interactive data |
| CN104199725A (en) * | 2014-09-27 | 2014-12-10 | 上海瀚之友信息技术服务有限公司 | Service interface data simulation method and system |
| CN104980464A (en) * | 2014-04-08 | 2015-10-14 | 北京奇虎科技有限公司 | Network request processing method, network server and network system |
| CN105450602A (en) * | 2014-08-21 | 2016-03-30 | 北大方正集团有限公司 | Mobile terminal control method and apparatus |
| CN105760159A (en) * | 2016-02-01 | 2016-07-13 | 四川长虹电器股份有限公司 | Website developing method and system |
-
2016
- 2016-05-26 CN CN201610362332.3A patent/CN106055383A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103686852A (en) * | 2012-09-07 | 2014-03-26 | 中国移动通信集团贵州有限公司 | Method, device and wireless acceleration system for processing interactive data |
| CN102945078A (en) * | 2012-11-13 | 2013-02-27 | 深圳先进技术研究院 | Human-computer interaction equipment and human-computer interaction method |
| CN104980464A (en) * | 2014-04-08 | 2015-10-14 | 北京奇虎科技有限公司 | Network request processing method, network server and network system |
| CN105450602A (en) * | 2014-08-21 | 2016-03-30 | 北大方正集团有限公司 | Mobile terminal control method and apparatus |
| CN104199725A (en) * | 2014-09-27 | 2014-12-10 | 上海瀚之友信息技术服务有限公司 | Service interface data simulation method and system |
| CN105760159A (en) * | 2016-02-01 | 2016-07-13 | 四川长虹电器股份有限公司 | Website developing method and system |
Non-Patent Citations (1)
| Title |
|---|
| 匿名: ""完整的前端工程框架"", 《HTTP://WWW.BUBUKO.COM/INFODETAIL¬1206351.HTML》 * |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106598575A (en) * | 2016-11-30 | 2017-04-26 | 武汉斗鱼网络科技有限公司 | Front-end data simulation implementation method and system |
| CN106681922A (en) * | 2016-12-27 | 2017-05-17 | 广州唯品会信息科技有限公司 | Simulation server response method and system |
| CN108259520A (en) * | 2016-12-27 | 2018-07-06 | 北京国双科技有限公司 | A kind of data processing method and server |
| CN108268570A (en) * | 2017-01-04 | 2018-07-10 | 武汉斗鱼网络科技有限公司 | A kind of method and device of development interface |
| CN109271310A (en) * | 2017-07-18 | 2019-01-25 | 北京京东尚科信息技术有限公司 | The exploitation test method and device of mobile applications network function |
| CN109788010A (en) * | 2017-11-13 | 2019-05-21 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of data localization access |
| CN108600311A (en) * | 2018-03-21 | 2018-09-28 | 浙江口碑网络技术有限公司 | The method and device of client simulation interface data |
| CN108600311B (en) * | 2018-03-21 | 2020-08-04 | 浙江口碑网络技术有限公司 | Method and device for simulating interface data by client |
| CN109388425A (en) * | 2018-08-17 | 2019-02-26 | 东莞数汇大数据有限公司 | A kind of interface switching method, system, device and the storage medium of front end engineering |
| CN109768951A (en) * | 2018-08-17 | 2019-05-17 | 付东光 | Remote analog data method and remote dummy server |
| CN109388425B (en) * | 2018-08-17 | 2021-08-31 | 东莞数汇大数据有限公司 | Interface switching method, system, device and storage medium for front-end engineering |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106055383A (en) | Request processing method and device | |
| US9949149B2 (en) | Online and distributed optimization framework for wireless analytics | |
| CN108494860B (en) | WEB access system, WEB access method and device for client | |
| JP2021103506A (en) | Method and device for generating information | |
| CN107480277B (en) | Method and device for collecting website logs | |
| CN110297944B (en) | Distributed XML data processing method and system | |
| CN107302597B (en) | Message file pushing method and device | |
| US10284671B2 (en) | Dynamic bundling of web components for asynchronous delivery | |
| US10592399B2 (en) | Testing web applications using clusters | |
| CN103268319A (en) | Cloud browser based on webpages | |
| CN112684968A (en) | Page display method and device, electronic equipment and computer readable medium | |
| CN105721462A (en) | Information pushing method and device | |
| CN108810047B (en) | Method and device for determining information push accuracy rate and server | |
| CN107305528B (en) | Application testing method and device | |
| CN105488205A (en) | Page generation method and page generation apparatus | |
| CN111680799A (en) | Method and apparatus for processing model parameters | |
| CN110866040A (en) | User portrait generation method, device and system | |
| CN111783005B (en) | Method, device and system for displaying web page, computer system and medium | |
| CN113505302A (en) | Method, device and system for supporting dynamic acquisition of buried point data and electronic equipment | |
| CN111754600A (en) | Poster image generation method and device and electronic equipment | |
| CN111787041A (en) | Method and apparatus for processing data | |
| CN112558933B (en) | Component rendering method and device, readable medium and electronic equipment | |
| CN105119764A (en) | Method and device for monitoring flow | |
| CN105224870A (en) | Suspected virus applies the method and apparatus uploaded | |
| CN113378346A (en) | Method and device for model simulation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20161026 |
|
| RJ01 | Rejection of invention patent application after publication |