CN107995259A - A kind of method and device handled cross-domain request - Google Patents

A kind of method and device handled cross-domain request Download PDF

Info

Publication number
CN107995259A
CN107995259A CN201711122866.XA CN201711122866A CN107995259A CN 107995259 A CN107995259 A CN 107995259A CN 201711122866 A CN201711122866 A CN 201711122866A CN 107995259 A CN107995259 A CN 107995259A
Authority
CN
China
Prior art keywords
recipient
resource request
resource
identification information
information
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
CN201711122866.XA
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.)
Beijing Si Tech Information Technology Co Ltd
Original Assignee
Beijing Si Tech Information Technology 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 Beijing Si Tech Information Technology Co Ltd filed Critical Beijing Si Tech Information Technology Co Ltd
Priority to CN201711122866.XA priority Critical patent/CN107995259A/en
Publication of CN107995259A publication Critical patent/CN107995259A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/565Conversion or adaptation of application format or content
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/955Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566URL specific, e.g. using aliases, detecting broken or misspelled links
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The present invention relates to a kind of method and device handled cross-domain request.This method is performed by Nginx servers, is specifically included:The resource request that sender sends is obtained, identification information corresponding with the recipient for receiving resource request is carried wherein in resource request;When determining that resource request is asked for cross-domain resource according to identification information, determine that recipient receives the form of data according to identification information;And the form that resource request is received to data according to recipient is changed, and obtains transformed resource request;Transformed resource request is sent to recipient.In processing procedure, as long as by a repeating process, it is possible to solve the problems, such as cross-domain.So as to avoid after multiple systems are integrated, the problem of some system wants to obtain suffered cross-domain limitation during the resource of other systems.

Description

A kind of method and device handled cross-domain request
Technical field
The present invention relates to field of telecommunications, more particularly to a kind of method and device handled cross-domain request.
Background technology
At present, it is different according to the function of Operation Support System, and business complexity, it is necessary to which core business is drawn Point, therefore establish numerous management platforms.Such as channel center, trade company center, affiliate center, channel direct-furnish platform, knot Calculation center, reward center, retail trader transaction APP, agent's supporting APP, supplier's transaction APP, Carrier Management APP etc. Deng.The page style of these platforms, technological frame, developer, system maintenance business are different.Affiliate enterprise is into industry During business management, due to needing cross-platform operation, necessarily cause inconvenience.
The content of the invention
To solve above-mentioned technical problem, the present invention provides a kind of method and device handled cross-domain request.
In a first aspect, the present invention provides a kind of method handled cross-domain request, this method is by Nginx servers Perform, specifically include:
The resource request that sender sends is obtained, is carried wherein in resource request corresponding with the recipient for receiving resource request Identification information;
When determining that resource request is asked for cross-domain resource according to identification information, determine that recipient receives the form of data;
And the form that resource request is received to data according to recipient is changed, and obtains transformed resource request;
Transformed resource request is sent to recipient.
The invention has the advantages that when the resource request for determining that sender sends is asked for cross-domain resource, Ke Yizhi The forwarding of Nginx servers was connected, and before forwarding, Nginx can turn resource request according to the identification information of recipient The form that recipient can identify is changed to, so that recipient can feed back corresponding information to sender according to resource request. In processing procedure, forwarded by Nginx server process, it is possible to solve the problems, such as cross-domain.So as to avoid in integrated multiple systems After system, the problem of some system wants to obtain suffered cross-domain limitation during the resource of other systems.
Further, after obtaining the resource request that sender sends, method further includes:
According to the identification information of recipient, the transmission path information of configuration sender to recipient;
According to transmission path information, transformed resource request is sent to recipient.
Advantageous effects using above-mentioned further scheme are, sender is configured according to the identification information of recipient To the transmission path of recipient, the resource request after turning is sent to recipient, it is convenient and efficient.
Further, according to the identification information of recipient, the transmission path information of configuration sender to recipient, specific bag Include:
According to identification information, generation universal resource locator (the Uniform Resource corresponding with identification information Locator, abbreviation URL);
According to URL, the transmission path information of configuration sender to recipient.
Advantageous effects using above-mentioned further technical solution are, according to URL, determine sender to recipient Transmission path information after, Nginx servers accurate can send resource request to recipient.
Further, the identification information of recipient includes:The address information of recipient, domain-name information, port information and One or more in subdomain name information.
Further, after transformed resource request being sent to recipient, method further includes:
Receive the resource fed back according to resource request of recipient, and by resource forwarding to sender.Second aspect, the present invention A kind of device handled cross-domain request is provided, which includes:
Acquiring unit, being carried for obtaining the resource request of sender's transmission, wherein in resource request please with receiving resource The corresponding identification information of recipient asked;
Processing unit, for when determining that resource request is asked for cross-domain resource according to identification information, determining that recipient connects Receive the form of data;
Converting unit, the form for resource request to be received to data according to recipient are changed, obtained transformed Resource request;
Transmitting element, for transformed resource request to be sent to recipient.
The advantageous effects of such scheme are, when the resource request for determining sender's transmission is that cross-domain resource is asked When, can directly it be forwarded by Nginx servers, and before forwarding, Nginx be able to will be provided according to the identification information of recipient Source request is converted to the form that recipient can identify, so that recipient can feed back corresponding information to hair according to resource request The side of sending.In processing procedure, forwarded by Nginx server process, it is possible to solve the problems, such as cross-domain.So as to avoid integrated After multiple systems, the problem of some system wants to obtain suffered cross-domain limitation during the resource of other systems..
Further, which further includes:
Dispensing unit, for the identification information according to recipient, the transmission path information of configuration sender to recipient;
Transmitting element is specifically used for, and according to transmission path information, transformed resource request is sent to recipient.
Advantageous effects using above-mentioned further scheme are, sender is configured according to the identification information of recipient To the transmission path of recipient, the resource request after turning is sent to recipient, it is convenient and efficient.
Further, dispensing unit is specifically used for:
According to identification information, the generation URL corresponding with identification information;
According to URL, the transmission path information of configuration sender to recipient.
Advantageous effects using above-mentioned further technical solution are, according to URL, determine sender to recipient Transmission path information after, Nginx servers accurate can send resource request to recipient.
Further, the identification information of recipient includes:The address information of recipient, domain-name information, port information and One or more in subdomain name information.
Further, which further includes:Receiving unit, the resource fed back for receiving recipient according to resource request, And by resource forwarding to sender.
Brief description of the drawings
Fig. 1 is a kind of method flow schematic diagram handled cross-domain request provided in an embodiment of the present invention;
Fig. 2 is the method flow schematic diagram that another kind provided in an embodiment of the present invention handles cross-domain request;
Fig. 3 is a kind of apparatus structure schematic diagram handled cross-domain request provided in an embodiment of the present invention.
Embodiment
In being described below, in order to illustrate rather than in order to limit, it is proposed that such as particular system structure, interface, technology it The detail of class, understands the present invention to cut thoroughly.However, it will be clear to one skilled in the art that these are specific The present invention can also be realized in the other embodiments of details.In other situations, omit to well-known system, circuit and The detailed description of method, in case unnecessary details hinders description of the invention.
Fig. 1 is a kind of method flow schematic diagram handled cross-domain request provided in an embodiment of the present invention.Specifically such as Shown in Fig. 1, this method includes:
Step 110, the resource request that sender sends is obtained.
Specifically, identification information corresponding with the recipient for receiving the resource request can be carried in giant resource requests.
Step 120, when determining that resource request is asked for cross-domain resource according to identification information, determine that recipient receives data Form.
Specifically, since the data format that different system application fields can identify may be different, then, in order to realize During cross-domain request resource, then the data format that can identify the format conversion of resource request for recipient is needed.Therefore, true Determine resource request for cross-domain resource request when, first have to determine recipient receive data form.Then step 130 is performed.
Step 130, the form for and by resource request according to recipient receiving data is changed, and obtains transformed resource Request.
Step 140, transformed resource request is sent to recipient.
Specifically, transformed resource request is sent to recipient, so that recipient can identify the resource request.
A kind of method handled cross-domain request provided in an embodiment of the present invention, when the resource for determining sender's transmission When asking to ask for cross-domain resource, can directly it be forwarded by Nginx servers, and before forwarding, Nginx can be according to connecing Resource request is converted to the form that recipient can identify by the identification information of debit, so that recipient can be according to resource request Corresponding information is fed back to sender.In processing procedure, forwarded by Nginx server process, it is possible to solve cross-domain Problem.So as to avoid after multiple systems are integrated, some system wants to obtain cross-domain limit suffered during the resource of other systems The problem of processed.
For the technical solution that the further description present invention is realized, the embodiment of the present invention additionally provides another right The method that cross-domain request is handled is specific as shown in Fig. 2, Fig. 2 is provided in an embodiment of the present invention another to cross-domain request The method flow schematic diagram handled.This method includes:
Step 210, the resource request that sender sends is obtained.
Specifically, identification information corresponding with the recipient for receiving the resource request can be carried in the resource request.Its In, the identification information of recipient can include:Address information, domain-name information, port information and the subdomain name information of recipient In one or more.
Step 250, according to the identification information of recipient, the transmission path information of configuration sender to recipient.
Specifically, the URL corresponding with identification information can be generated according to identification information.
Then according to URL, the transmission path information of configuration sender to recipient.Configuring transmission path information can be Configured in nginx configuration files nginx.conf.And in URL, can be with when determining resource request being distributed to which system Pre-configured field identification in URL.For example, carrying " dform " in url field, then explanation needs to send out resource request Send to dynamic list.And when carrying " uop " in url field, then explanation needs to send resource request to calling interface tune With service.
In specific implementation process, such as user, after page input keyword (identification information of recipient), system obtains To the keyword message.The page performs the JavaScript method of response, is called and serviced by ajax, generates a request resource URL.Then by the configuration path in nginx configuration files nginx.conf, then after step 220-230, will turn Resource request after changing is sent to recipient.It is specific as follows:
Step 220, when determining that resource request is asked for cross-domain resource according to identification information, determine that recipient receives data Form.
Specifically, since the data format that different system application fields can identify may be different, then, in order to realize During cross-domain request resource, then the data format that can identify the format conversion of resource request for recipient is needed.Therefore, true Determine resource request for cross-domain resource request when, first have to determine recipient receive data form.Then step 230 is performed.
Step 230, the form for and by resource request according to recipient receiving data is changed, and obtains transformed resource Request.
Step 240, transformed resource request is sent to recipient.
Specifically, transformed resource request is sent to recipient, so that recipient can identify the resource request.
After recipient receives resource request, it will necessarily respond, then again will resource corresponding with resource request Pass through Nginx server feedbacks to sender, i.e. step 260.
Step 260, the resource fed back according to resource request of recipient is received, and by resource forwarding to sender.
A kind of method handled cross-domain request provided in an embodiment of the present invention, when the resource for determining sender's transmission When asking to ask for cross-domain resource, can directly it be forwarded by Nginx servers, and before forwarding, Nginx can be according to connecing Resource request is converted to the form that recipient can identify by the identification information of debit, so that recipient can be according to resource request Corresponding information is fed back to sender.In processing procedure, forwarded by Nginx server process, it is possible to solve cross-domain Problem.So as to avoid after multiple systems are integrated, some system wants to obtain cross-domain limit suffered during the resource of other systems The problem of processed.At the same time the efficiency of system will not be caused to reduce.Moreover, frequency of maintenance will substantially reduce, once configuration is completed, Forward-path need not make an amendment again substantially, enter unless there are new forward-path, can just do an appropriate adjustment.
After configuration file adjustment, then need to restart Nginx servers, come into force to configure adjustment.Performing form The follow-up works such as conversion.
Correspondingly, the embodiment of the present invention additionally provides a kind of device handled cross-domain request.Fig. 3 is real for the present invention A kind of apparatus structure schematic diagram handled cross-domain request of example offer is provided.As shown in figure 3, the device includes:Obtain single Member 301, processing unit 302, converting unit 303 and transmitting element 304.
Acquiring unit 301, for obtaining the resource request of sender's transmission, carries with receiving resource wherein in resource request The corresponding identification information of recipient of request.Wherein, the identification information of recipient includes:The address information of recipient, domain name letter One or more in breath, port information and subdomain name information.
Processing unit 302, for when determining that resource request is asked for cross-domain resource according to identification information, determining recipient Receive the form of data.
Converting unit 303, the form for resource request to be received to data according to recipient is changed, after obtaining conversion Resource request.
Transmitting element 304, for transformed resource request to be sent to recipient.
Optionally, which can also include:Dispensing unit 305, for the identification information according to recipient, configuration is sent The square transmission path information to recipient.
Transmitting element 304 is specifically used for, and according to transmission path information, transformed resource request is sent to recipient.
Further alternative, dispensing unit 305 is specifically used for:It is corresponding with identification information according to identification information, generation URL.According to URL, the transmission path information of configuration sender to recipient.
Further alternative, which can also include:Receiving unit 306, for receiving recipient according to resource request The resource of feedback, and by resource forwarding to sender.
A kind of device handled cross-domain request provided in an embodiment of the present invention, when the resource for determining sender's transmission When asking to ask for cross-domain resource, can directly it be forwarded by Nginx servers, and before forwarding, Nginx can be according to connecing Resource request is converted to the form that recipient can identify by the identification information of debit, so that recipient can be according to resource request Corresponding information is fed back to sender.In processing procedure, forwarded by Nginx server process, it is possible to solve cross-domain Problem.So as to avoid after multiple systems are integrated, some system wants to obtain cross-domain limit suffered during the resource of other systems The problem of processed.At the same time the efficiency of system will not be caused to reduce.Moreover, frequency of maintenance will substantially reduce, once configuration is completed, Forward-path need not make an amendment again substantially, enter unless there are new forward-path, can just do an appropriate adjustment.Configuration file After adjustment, then need to restart Nginx servers, come into force to configure adjustment.Performing the follow-up works such as format conversion.
Reader should be understood that in the description of this specification, reference term " one embodiment ", " some embodiments ", " show The description of example ", " specific example " or " some examples " etc. mean to combine the specific features of the embodiment or example description, structure, Material or feature are contained at least one embodiment of the present invention or example.In the present specification, above-mentioned term is shown The statement of meaning property need not be directed to identical embodiment or example.Moreover, particular features, structures, materials, or characteristics described It may be combined in any suitable manner in any one or more of the embodiments or examples.In addition, without conflicting with each other, this The technical staff in field can be by the different embodiments or example described in this specification and different embodiments or exemplary spy Sign is combined and combines.
Although the embodiment of the present invention has been shown and described above, it is to be understood that above-described embodiment is example Property, it is impossible to limitation of the present invention is interpreted as, those of ordinary skill in the art within the scope of the invention can be to above-mentioned Embodiment is changed, changes, replacing and modification.

Claims (10)

  1. A kind of 1. method handled cross-domain request, it is characterised in that the method is performed by Nginx servers, described Method includes:
    The resource request that sender sends is obtained, wherein carrying the recipient with receiving the resource request in the resource request Corresponding identification information;
    When determining that the resource request is asked for cross-domain resource according to the identification information, determine that the recipient receives data Form;
    And the form that the resource request is received to data according to the recipient is changed, obtaining transformed resource please Ask;
    The transformed resource request is sent to the recipient.
  2. 2. according to the method described in claim 1, it is characterized in that, it is described obtain sender send resource request after, institute The method of stating further includes:
    According to the identification information of the recipient, the transmission path information of configuration described sender to the recipient;
    According to the transmission path information, the transformed resource request is sent to the recipient.
  3. 3. according to the method described in claim 2, it is characterized in that, the identification information according to the recipient, configures institute Sender is stated to the transmission path information of the recipient, is specifically included:
    According to the identification information, the generation uniform resource position mark URL corresponding with the identification information;
    According to the URL, the transmission path information of configuration described sender to the recipient.
  4. 4. according to claim 1-3 any one of them methods, it is characterised in that the identification information of the recipient includes:Institute State the one or more in address information, domain-name information, port information and the subdomain name information of recipient.
  5. 5. according to claim 1-3 any one of them methods, it is characterised in that described to send out the transformed resource request After giving the recipient, the method further includes:
    Receive the resource that the recipient feeds back according to the resource request, and by the resource forwarding to sender.
  6. 6. a kind of device handled cross-domain request, it is characterised in that described device includes:
    Acquiring unit, for obtaining the resource request of sender's transmission, wherein being carried in the resource request with receiving the money The corresponding identification information of recipient of source request;
    Processing unit, for when determining that the resource request is asked for cross-domain resource according to the identification information, determining described Recipient receives the form of data;
    Converting unit, the form for the resource request to be received to data according to the recipient are changed, and obtain conversion Resource request afterwards;
    Transmitting element, for the transformed resource request to be sent to the recipient.
  7. 7. device according to claim 6, it is characterised in that described device further includes:
    Dispensing unit, for the identification information according to the recipient, configuration described sender to the transmission road of the recipient Footpath information;
    The transmitting element is specifically used for, and according to the transmission path information, the transformed resource request is sent to institute State recipient.
  8. 8. device according to claim 7, it is characterised in that the dispensing unit is specifically used for:
    According to the identification information, the generation URL corresponding with the identification information;
    According to the URL, the transmission path information of configuration described sender to the recipient.
  9. 9. according to claim 6-8 any one of them devices, it is characterised in that the identification information of the recipient includes:Institute State the one or more in address information, domain-name information, port information and the subdomain name information of recipient.
  10. 10. according to claim 6-8 any one of them devices, it is characterised in that described device further includes:
    Receiving unit, the resource fed back for receiving the recipient according to the resource request, and by the resource forwarding extremely Sender.
CN201711122866.XA 2017-11-14 2017-11-14 A kind of method and device handled cross-domain request Pending CN107995259A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711122866.XA CN107995259A (en) 2017-11-14 2017-11-14 A kind of method and device handled cross-domain request

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711122866.XA CN107995259A (en) 2017-11-14 2017-11-14 A kind of method and device handled cross-domain request

Publications (1)

Publication Number Publication Date
CN107995259A true CN107995259A (en) 2018-05-04

Family

ID=62031371

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711122866.XA Pending CN107995259A (en) 2017-11-14 2017-11-14 A kind of method and device handled cross-domain request

Country Status (1)

Country Link
CN (1) CN107995259A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109688280A (en) * 2018-08-21 2019-04-26 平安科技(深圳)有限公司 Request processing method, request processing equipment, browser and storage medium
CN109918602A (en) * 2019-02-26 2019-06-21 南威软件股份有限公司 A kind of web data preloading method and system
CN110309499A (en) * 2019-07-05 2019-10-08 广东铭太信息科技有限公司 Method for generating the device and online generation examination report of examination report
CN110728118A (en) * 2019-09-10 2020-01-24 中国平安人寿保险股份有限公司 Cross-data-platform data processing method, device, equipment and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102843437A (en) * 2012-09-17 2012-12-26 北京星网锐捷网络技术有限公司 Conversion method and device for webpage application and network device
CN103309861A (en) * 2012-03-07 2013-09-18 阿里巴巴集团控股有限公司 Method and device for acquiring cross-domain data
WO2014157222A1 (en) * 2013-03-29 2014-10-02 Kddi株式会社 Web-content delivery device
CN104410711A (en) * 2014-12-15 2015-03-11 北京国双科技有限公司 Cross-domain network resource request method and device for client
CN106878408A (en) * 2017-02-08 2017-06-20 福建天泉教育科技有限公司 The method and system of cross-domain request data

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103309861A (en) * 2012-03-07 2013-09-18 阿里巴巴集团控股有限公司 Method and device for acquiring cross-domain data
CN102843437A (en) * 2012-09-17 2012-12-26 北京星网锐捷网络技术有限公司 Conversion method and device for webpage application and network device
WO2014157222A1 (en) * 2013-03-29 2014-10-02 Kddi株式会社 Web-content delivery device
CN104410711A (en) * 2014-12-15 2015-03-11 北京国双科技有限公司 Cross-domain network resource request method and device for client
CN106878408A (en) * 2017-02-08 2017-06-20 福建天泉教育科技有限公司 The method and system of cross-domain request data

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109688280A (en) * 2018-08-21 2019-04-26 平安科技(深圳)有限公司 Request processing method, request processing equipment, browser and storage medium
CN109918602A (en) * 2019-02-26 2019-06-21 南威软件股份有限公司 A kind of web data preloading method and system
CN110309499A (en) * 2019-07-05 2019-10-08 广东铭太信息科技有限公司 Method for generating the device and online generation examination report of examination report
CN110309499B (en) * 2019-07-05 2020-07-17 广东铭太信息科技有限公司 Device for generating examination report and method for generating examination report online
CN110728118A (en) * 2019-09-10 2020-01-24 中国平安人寿保险股份有限公司 Cross-data-platform data processing method, device, equipment and storage medium
CN110728118B (en) * 2019-09-10 2023-07-25 中国平安人寿保险股份有限公司 Cross-data-platform data processing method, device, equipment and storage medium

Similar Documents

Publication Publication Date Title
CN107995259A (en) A kind of method and device handled cross-domain request
US9009599B2 (en) Technique for handling URLs for different mobile devices that use different user interface platforms
CN114020378A (en) Method and system for processing digital components
CN104144206A (en) Method, system and device for loading interface
CN109104368B (en) Connection request method, device, server and computer readable storage medium
CN109857577B (en) Access control method, device, medium, and electronic apparatus
CN108924183B (en) Method and device for processing information
US20190370293A1 (en) Method and apparatus for processing information
CN111950249A (en) Message generation method and device, electronic equipment and storage medium
CN112817562B (en) Service processing method and device
CN113535101B (en) Print file generation method and device, storage medium and electronic equipment
CN108076110B (en) Electronic data exchange system and apparatus comprising an electronic data exchange system
CN109829708B (en) Transaction processing system
CN113760482A (en) Task processing method, device and system
CN109005250B (en) Method and device for accessing server
US10203965B2 (en) Data processing method and system for intercepting signals between a peripheral device and a software application
CN107171959B (en) Dynamic routing method and dynamic routing system based on SOA (service oriented architecture)
CN105871972A (en) Video resource distributed cathe method, device and system
US8832199B2 (en) Method and apparatus for connecting devices
CN107977380B (en) Method and device for generating page
CN112445987B (en) Webpage updating method, device and system
CN113760582A (en) Document declaration method and device
CN112836201A (en) Method, device, equipment and computer readable medium for multi-platform information intercommunication
CN113760279A (en) Method and device for generating page
CN114666750A (en) Message fallback method and device, message processing equipment and MaaP platform equipment

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
RJ01 Rejection of invention patent application after publication

Application publication date: 20180504

RJ01 Rejection of invention patent application after publication