WO2017041657A1 - Procédé et dispositif de gestion d'interface d'application - Google Patents

Procédé et dispositif de gestion d'interface d'application Download PDF

Info

Publication number
WO2017041657A1
WO2017041657A1 PCT/CN2016/097505 CN2016097505W WO2017041657A1 WO 2017041657 A1 WO2017041657 A1 WO 2017041657A1 CN 2016097505 W CN2016097505 W CN 2016097505W WO 2017041657 A1 WO2017041657 A1 WO 2017041657A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
application interface
annotation information
authentication
module
Prior art date
Application number
PCT/CN2016/097505
Other languages
English (en)
Chinese (zh)
Inventor
陈晓丹
Original Assignee
阿里巴巴集团控股有限公司
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 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017041657A1 publication Critical patent/WO2017041657A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating

Definitions

  • the present application relates to the field of computers, and in particular, to an application interface management method and apparatus.
  • the existing information system In addition to the requirements of completing the service, the existing information system generally needs to set up an open interface to provide external services through the API (Application Programming Interface), and the corresponding service process is accompanied by corresponding The return of indicator data; where the indicator generally refers to the type of data returned by the interface call. For the security of the data, it is generally necessary to check the identity of the caller, and at the same time, it is necessary to control the granularity of the returned indicator according to the identity of the caller.
  • API Application Programming Interface
  • An object of the present application is to provide an application interface management method and apparatus to solve the problem of implementing application interface call management when the existing code is not changed on a large scale or the code body logic is not changed.
  • an application interface management method includes:
  • the call of the application interface is managed according to the annotation information and the call request.
  • an application interface management apparatus wherein the apparatus includes:
  • An interception module for intercepting a call request to an application interface
  • An obtaining module configured to obtain annotation information of the application interface
  • Calling a management module configured to perform, according to the annotation information and the call request, the call of the application interface management.
  • the application interface management method and apparatus provided by the present application does not affect the execution logic of the existing code of the application interface because the increase of the annotation information does not need to change the existing code or the code body on a large scale.
  • the logic changes only need to add annotation information to the existing application interface, and correspondingly introduce additional processing logic, you can manage the interface of different granularity for each interface that is open, thus reducing the value overhead caused by code maintenance. .
  • FIG. 1 is a flow chart showing an application interface management method according to an aspect of the present application
  • FIG. 2 is a schematic flow chart of an application interface management method according to still another aspect of the present application.
  • FIG. 3 is a schematic structural diagram of an application interface management apparatus according to an aspect of the present application.
  • FIG. 4 shows a schematic structural diagram of an application interface management apparatus according to still another aspect of the present application.
  • FIG. 1 is a flow chart showing an application interface management method according to an aspect of the present application. As shown in FIG. 1, the application interface management method includes:
  • Step S101 intercepting a call request to an application interface
  • Step S102 Obtain annotation information of the application interface.
  • Step S103 managing the call of the application interface according to the annotation information and the call request.
  • the application interface refers to an API interface.
  • the API interface is pre-added with annotation information, such as Annotation annotation information provided by the Java language, and the annotation information includes management information for calling the API interface, such as management information for calling authentication and index filtering.
  • annotation information can be processed by AOP (Aspect Oriented Programming) technology to control the call of the API interface.
  • annotation information will not It affects the execution logic of the existing code of the application interface. Therefore, when managing the application interface call, there is no need to change the existing code or change the logic of the code main body on a large scale, and only need to manage the code through the independently added application interface. According to the annotation information, the call management of each application interface can be realized, thereby reducing the value overhead caused by code maintenance, for example, avoiding the service failure caused by the modification of the main logic.
  • the annotation information includes calling authentication information
  • the managing the call of the application interface according to the annotation information and the calling request further includes:
  • the call authentication is divided into two kinds of results, the call authentication is passed, and the call to the API interface is executed at this time; the call authentication is not passed, for example, the identity of the caller does not comply with the call permission of the API interface, and according to the return value Type, wrap the error message and return directly.
  • managing the call of the application interface according to the annotation information and the calling request further includes:
  • the caller of the API interface does not perform call authentication and directly executes the API interface call.
  • annotation information further includes indicator filtering information
  • the managing the call of the application interface according to the annotation information and the calling request further includes:
  • the returned result filtered by the indicator is returned.
  • the return result obtained by directly executing the API interface call may be returned, or the return result obtained by executing the API interface call after the authentication is invoked may be filtered by the indicator. Go back.
  • managing the call of the application interface according to the annotation information and the calling request further includes:
  • the return result obtained by directly executing the API interface call may be returned, or the return result obtained by executing the API interface call after the authentication is invoked may be not filtered. , return directly and end the entire process.
  • the method further includes:
  • the class that processes the annotation information can be created in a face-oriented manner.
  • annotation information is added in advance using the Annotation mechanism provided by the Java language, and the annotation information added by the Annotation does not affect the execution logic of the existing code.
  • the aspect-oriented approach refers to AOP (Aspect Oriented Programming), a technique for achieving unified maintenance of program functions through precompilation and runtime dynamic agents.
  • the classes used to process annotation information are newly added and do not require changes to the concrete implementation logic of the existing application interface.
  • the application interface calling method includes:
  • Step S201 adding the annotation information to the application interface.
  • annotation information is added by the Annotation mechanism provided by the Java language, and the annotation information added by the Annotation does not affect the execution logic of the existing code.
  • the annotation information includes the call authentication information and the indicator filtering information. In addition, it may also include information on whether interface management is required, for example, whether the API authentication interface needs to be invoked, or whether the API interface needs to be invoked. Returns the result for metric filtering.
  • the call authentication information may include information such as an authentication processing object
  • the indicator filtering information may include information such as an indicator filtering object.
  • the indicator can refer to the data category returned by the interface calling the API interface.
  • Step S202 creating a class for processing the annotation information.
  • the class that processes the annotation information can be created in a face-oriented manner, and the aspect-oriented approach refers to the AOP mode.
  • the classes used to process annotation information are newly added and do not require changes to the concrete implementation logic of the existing application interface.
  • Step S203 intercepting the calling request of the application interface and acquiring the annotation information of the application interface.
  • the service requester the API interface caller
  • the AOP intercepts the call request and parses the Annotation annotation information that has been added by the API interface to obtain the data information required for subsequent API interface call management.
  • step S204 it is determined whether call authentication needs to be performed.
  • the judgment is made based on whether or not information required for interface management is included in the annotation information. For example, it is determined based on whether or not the information to be called for authentication is set in advance to the API interface.
  • Step S205 when the call authentication is not required, the call to the application interface is directly executed.
  • the caller of the API interface does not perform call authentication and directly executes the API interface call.
  • the process may go to step S209 to determine whether it is necessary to perform index filtering on the returned result.
  • Step S206 When the call authentication needs to be performed, call the authentication request according to the call authentication information.
  • the call authentication is divided into two kinds of results, the call authentication is passed, and the process jumps to step S208 for processing; the call authentication is not passed, for example, the identity of the caller does not comply with the call permission of the API interface, and the jump is performed at this time.
  • the process proceeds to step S207.
  • Step S207 When the call authentication fails, the error prompt information is returned.
  • the error message is wrapped and returned directly to the end of the process.
  • Step S208 after the call authentication is passed, perform a call to the application interface.
  • the identity of the caller conforms to the call permission setting of the API interface, and the call authentication is allowed to pass. After the API interface is called and the returned result is obtained, the process proceeds to step S209 to determine.
  • step S209 it is determined whether index filtering is required.
  • the judgment is made based on whether or not information required for interface management is included in the annotation information. For example, it is determined based on whether or not the information required to be filtered by the API interface is set in advance. The judgment is divided into two kinds of results, and the indicator filtering is not required, and the process proceeds to step S210 for processing; the indicator filtering is required, and the process proceeds to step S211 for processing.
  • step S210 when the indicator filtering is not required, the return result after the execution of the call is directly returned.
  • the return result obtained by directly executing the API interface call in step S205, or the return result obtained by executing the API interface call after the authentication is passed in step S208 Without metric filtering, go straight back and end the entire process.
  • step S211 when the indicator filtering needs to be performed, the indicator filtering is performed on the returned result after the call is performed according to the indicator filtering information.
  • step S212 the returned result filtered by the indicator is returned.
  • the API interface is preset to require index filtering
  • the return result obtained by directly executing the call of the API interface in step S205 or the return result obtained by executing the API interface call after calling the authentication in step S208
  • the metric granularity of the returned metrics can be controlled according to the identity of the caller.
  • FIG. 3 shows a schematic structural diagram of an application interface management apparatus according to an aspect of the present application.
  • the application interface management apparatus 3 includes an interception module 31, an acquisition module 32, and an invocation management module 33.
  • the intercepting module 31 is configured to intercept a call request to the application interface
  • the obtaining module 32 is configured to obtain the annotation information of the application interface
  • the calling management module 33 is configured to perform, according to the annotation information and the calling request The call of the application interface is managed.
  • the intercepting module 31 intercepts the call request sent by the caller to the API interface, and sends it to the call management module 33 for processing; the obtaining module 32 acquires the pre-added annotation information from the API interface, and sends the annotation information to the call management module 33. deal with.
  • the API interface is pre-added with annotation information, such as Annotation annotation information provided by the Java language, and the annotation information includes management information for calling the API interface, such as management information for calling authentication and index filtering.
  • the call management module 33 performs call authentication management according to the call authentication information in the annotation information, performs identity control on the caller of the API interface, that is, the service user, or returns the information to the API interface according to the index filtering information in the annotation information. The granularity of the indicators is controlled and managed.
  • the application interface management device of the present application does not need to change the existing code or modify the logic of the code main body on a large scale, and only needs to manage the code through the independently added application interface, and can process the call to each application interface according to the annotation information. Management, thereby reducing the value overhead of code maintenance, such as avoiding service failures due to changes in the subject logic.
  • FIG. 4 shows a schematic structural diagram of an application interface management apparatus according to still another aspect of the present application.
  • the application interface management apparatus 4 includes: an interception module 31, an acquisition module 32, and an invocation management module 33 shown in FIG. 3, and an annotation module 41 and a processing class module 42.
  • the intercepting module 31 is configured to intercept a call request to the application interface
  • the obtaining module 32 is configured to obtain the annotation information of the application interface
  • the calling management module 33 is configured to perform, according to the annotation information and the calling request The call of the application interface is managed.
  • the intercepting module 31 intercepts the call request sent by the caller to the API interface, and sends it to the call management module 33 for processing; the obtaining module 32 acquires the pre-added annotation information from the API interface, and sends the annotation information to the call management module 33. deal with.
  • the annotation module 41 is configured to add the annotation information to the application interface.
  • the annotation information does not affect the execution logic of the existing code.
  • the annotation information includes the call authentication information and the indicator filtering information, and may also include information about whether interface management is required, for example, whether it is necessary.
  • the API interface performs information for invoking authentication, or whether it needs to perform index filtering on the returned result of calling the API interface.
  • the call authentication information may include information such as an authentication processing object
  • the indicator filtering information may include information such as an indicator filtering object.
  • the indicator can refer to the data category returned by the interface calling the API interface.
  • the processing class module 42 is configured to create a class that processes the annotation information.
  • the processing class module 42 is further configured to: create a class that processes the annotation information in a face-oriented manner.
  • the class used to process the annotation information is newly added, and there is no need to change the concrete implementation logic class of the existing application interface.
  • the call management module 33 further includes: an authentication module 331, an execution calling module 332, and a first determining module 333.
  • the authentication module 331 is configured to perform call authentication on the call request according to the call authentication information.
  • the authentication module 331 is further configured to: return an error prompt message when the call authentication fails.
  • the execution invoking module 332 is configured to execute a call to the application interface after the call authentication is passed.
  • the execution invocation module 332 is further configured to directly perform a call to the application interface when call authentication is not required.
  • the first determining module 333 is configured to determine whether the call authentication needs to be performed before the call authentication is performed.
  • the first determining module 333 notifies the execution calling module 332 to directly execute the call to the application interface; when the call authentication needs to be performed, the first determining module 333 notifies the authentication module 331 to make the call. After the authentication is passed, the authentication module 331 notifies the execution calling module 332 to execute the API interface call; when the calling authentication fails, the authentication module 331 directly returns the error prompt information according to the return value type.
  • the call management module 33 further includes: an index filtering module 334, a return module 335, and a second determining module 336.
  • the metric filtering module 334 is configured to perform metric filtering on the return result after the application interface is invoked according to the metric filtering information.
  • the returning module 335 is configured to return the returned result filtered by the indicator.
  • the returning module 334 is further configured to: directly return a return result after the execution of the application interface call when the indicator filtering is not required.
  • the second determining module 336 is configured to determine whether the indicator filtering needs to be performed before performing the indicator filtering
  • the second determining module 336 When the metric filtering is not required, the second determining module 336 notifies the returning module 334 to directly return the return result obtained by the execution calling module 332.
  • the second determining module 336 passes The knowledge indicator filtering module 334 performs index filtering on the return result obtained by the execution calling module 332, and the return module 334 returns the returned result processed by the index filtering module 334.
  • the return result of the execution call module 332 can be obtained by directly executing the API interface call, or by calling the API interface call after the authentication is passed.
  • the present application can be implemented in software and/or a combination of software and hardware, for example, using an application specific integrated circuit (ASIC), a general purpose computer, or any other similar hardware device.
  • the software program of the present application can be executed by a processor to implement the steps or functions described above.
  • the software programs (including related data structures) of the present application can be stored in a computer readable recording medium such as a RAM memory, a magnetic or optical drive or a floppy disk and the like.
  • some of the steps or functions of the present application may be implemented in hardware, for example, as a circuit that cooperates with a processor to perform various steps or functions.
  • a portion of the present application can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide a method and/or technical solution in accordance with the present application.
  • the program instructions for invoking the method of the present application may be stored in a fixed or removable recording medium, and/or transmitted by a data stream in a broadcast or other signal bearing medium, and/or stored in a The working memory of the computer device in which the program instructions are run.
  • an embodiment in accordance with the present application includes a device including a memory for storing computer program instructions and a processor for executing program instructions, wherein when the computer program instructions are executed by the processor, triggering
  • the apparatus operates based on the aforementioned methods and/or technical solutions in accordance with various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé et un dispositif de gestion d'interface d'application. Ledit procédé consiste à : intercepter une requête d'appel pour une interface d'application (S101) ; acquérir des informations d'annotation de l'interface d'application (S102) ; et gérer l'appel de l'interface d'application conformément aux informations d'annotation et à la requête d'appel (S103). Par comparaison avec l'état antérieur de la technique, le procédé et le dispositif de gestion d'interface d'application de la présente invention fournissent, au moyen de l'ajout d'informations d'annotation aux codes existants, les informations requises pour la gestion de processus d'appel, ce qui ne nécessite aucun changement des codes existants sur une grande échelle ou de la logique principale des codes. La gestion de code au moyen d'interfaces d'application ajoutées de manière indépendante, et le traitement selon des informations d'annotation, permettent une gestion d'appel pour chaque interface d'application, ce qui réduit le coût résultant de la maintenance de code.
PCT/CN2016/097505 2015-09-09 2016-08-31 Procédé et dispositif de gestion d'interface d'application WO2017041657A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510570439.2A CN106528185A (zh) 2015-09-09 2015-09-09 一种应用接口管理方法和装置
CN201510570439.2 2015-09-09

Publications (1)

Publication Number Publication Date
WO2017041657A1 true WO2017041657A1 (fr) 2017-03-16

Family

ID=58240539

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/097505 WO2017041657A1 (fr) 2015-09-09 2016-08-31 Procédé et dispositif de gestion d'interface d'application

Country Status (2)

Country Link
CN (1) CN106528185A (fr)
WO (1) WO2017041657A1 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110489180A (zh) * 2019-08-07 2019-11-22 北京字节跳动网络技术有限公司 一种埋点上报方法、装置、介质和电子设备
US10496387B2 (en) 2018-04-03 2019-12-03 Microsoft Technology Licensing, Llc Crowdsourced API resource consumption information for integrated development environments
CN110908644A (zh) * 2019-10-16 2020-03-24 浙江大搜车软件技术有限公司 状态节点的配置方法、装置、计算机设备和存储介质
CN111191246A (zh) * 2019-12-19 2020-05-22 杭州安恒信息技术股份有限公司 一种基于Spring注解的安全开发校验方法
CN111414194A (zh) * 2020-03-19 2020-07-14 政采云有限公司 一种接口信息生成方法、系统、电子设备及存储介质
CN112398870A (zh) * 2020-11-30 2021-02-23 深圳市六度人和科技有限公司 跨平台协议生成方法、装置、系统、设备及存储介质
CN112632158A (zh) * 2019-09-24 2021-04-09 阿里巴巴集团控股有限公司 数据处理方法、设备及存储介质
CN113722733A (zh) * 2021-08-27 2021-11-30 北京航天云路有限公司 一种基于Java注解实现的数据访问权限控制方法
CN115174683A (zh) * 2022-06-29 2022-10-11 广州鲁邦通智能科技有限公司 一种调用查询接口的请求方法及系统

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110569299B (zh) * 2018-01-29 2023-04-18 北京数聚鑫云信息技术有限公司 一种基于api的管理系统及管理方法
CN109726081A (zh) * 2019-01-02 2019-05-07 深圳壹账通智能科技有限公司 业务异常处理的方法、装置、计算机设备和存储介质
CN110147261A (zh) * 2019-04-15 2019-08-20 平安普惠企业管理有限公司 基于调用接口的参数校验方法及相关设备
CN110045952B (zh) * 2019-04-19 2020-09-29 京东数字科技控股有限公司 代码调用方法与装置
CN110968296B (zh) * 2019-12-03 2023-07-25 政采云有限公司 一种数据获取方法、装置、设备及可读存储介质
CN111324394B (zh) * 2020-01-23 2023-05-12 北京恒华伟业科技股份有限公司 系统集成的方法和装置
CN111858101B (zh) * 2020-07-28 2023-05-26 深圳平安医疗健康科技服务有限公司 面向云架构系统的适配方法、装置、设备及存储介质
CN113127309B (zh) * 2021-04-30 2023-10-10 北京奇艺世纪科技有限公司 一种程序监控方法、装置、电子设备及存储介质
CN113313595A (zh) * 2021-06-25 2021-08-27 中国农业银行股份有限公司 交易处理方法、设备、存储介质及产品
CN113849789A (zh) * 2021-09-29 2021-12-28 中国平安财产保险股份有限公司 基于aop的权限校验方法、装置、设备及存储介质
CN113779638A (zh) * 2021-11-15 2021-12-10 浪潮软件股份有限公司 一种动态代理模式下实现接口调用方鉴权的方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103049271A (zh) * 2012-12-27 2013-04-17 微梦创科网络科技（中国）有限公司 自动生成api接口的描述文档的方法和装置
CN103399734A (zh) * 2013-07-10 2013-11-20 北京慧点科技股份有限公司 生成rest服务和rest实现的方法及对应的设备
CN103514026A (zh) * 2013-09-27 2014-01-15 摩卡软件(天津)有限公司 一种通过javascript直接调用java api的方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101276271A (zh) * 2007-03-29 2008-10-01 北京邮电大学 一种面向切面编程的拦截器系统及方法
CN102982130A (zh) * 2012-11-16 2013-03-20 深圳市融创天下科技股份有限公司 一种nosql与rdbms的数据库同步方法和系统
CN103412766A (zh) * 2013-09-05 2013-11-27 曙光云计算技术有限公司 基于用户权限的数据访问方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103049271A (zh) * 2012-12-27 2013-04-17 微梦创科网络科技（中国）有限公司 自动生成api接口的描述文档的方法和装置
CN103399734A (zh) * 2013-07-10 2013-11-20 北京慧点科技股份有限公司 生成rest服务和rest实现的方法及对应的设备
CN103514026A (zh) * 2013-09-27 2014-01-15 摩卡软件(天津)有限公司 一种通过javascript直接调用java api的方法

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10496387B2 (en) 2018-04-03 2019-12-03 Microsoft Technology Licensing, Llc Crowdsourced API resource consumption information for integrated development environments
CN110489180B (zh) * 2019-08-07 2023-03-28 北京字节跳动网络技术有限公司 一种埋点上报方法、装置、介质和电子设备
CN110489180A (zh) * 2019-08-07 2019-11-22 北京字节跳动网络技术有限公司 一种埋点上报方法、装置、介质和电子设备
CN112632158B (zh) * 2019-09-24 2024-05-10 阿里巴巴集团控股有限公司 数据处理方法、设备及存储介质
CN112632158A (zh) * 2019-09-24 2021-04-09 阿里巴巴集团控股有限公司 数据处理方法、设备及存储介质
CN110908644A (zh) * 2019-10-16 2020-03-24 浙江大搜车软件技术有限公司 状态节点的配置方法、装置、计算机设备和存储介质
CN110908644B (zh) * 2019-10-16 2023-12-12 浙江大搜车软件技术有限公司 状态节点的配置方法、装置、计算机设备和存储介质
CN111191246A (zh) * 2019-12-19 2020-05-22 杭州安恒信息技术股份有限公司 一种基于Spring注解的安全开发校验方法
CN111414194B (zh) * 2020-03-19 2023-08-11 政采云有限公司 一种接口信息生成方法、系统、电子设备及存储介质
CN111414194A (zh) * 2020-03-19 2020-07-14 政采云有限公司 一种接口信息生成方法、系统、电子设备及存储介质
CN112398870B (zh) * 2020-11-30 2022-09-13 深圳市六度人和科技有限公司 跨平台协议生成方法、装置、系统、设备及存储介质
CN112398870A (zh) * 2020-11-30 2021-02-23 深圳市六度人和科技有限公司 跨平台协议生成方法、装置、系统、设备及存储介质
CN113722733A (zh) * 2021-08-27 2021-11-30 北京航天云路有限公司 一种基于Java注解实现的数据访问权限控制方法
CN115174683A (zh) * 2022-06-29 2022-10-11 广州鲁邦通智能科技有限公司 一种调用查询接口的请求方法及系统
CN115174683B (zh) * 2022-06-29 2023-10-13 广州鲁邦通智能科技有限公司 一种调用查询接口的请求方法及系统

Also Published As

Publication number Publication date
CN106528185A (zh) 2017-03-22

Similar Documents

Publication Publication Date Title
WO2017041657A1 (fr) Procédé et dispositif de gestion d'interface d'application
WO2019153472A1 (fr) Procédé de test automatisé d'interfaces, dispositif, équipement, et support de stockage
US9092332B2 (en) Activity based sampling of diagnostics data
JP5985631B2 (ja) 信頼レベルのアクティブ化
WO2019024674A1 (fr) Procédé et appareil de traitement de contrat intelligent
US8434070B2 (en) Generating specifications of client-server applications for static analysis
WO2018045753A1 (fr) Procédé et dispositif de calcul de graphe distribué
US20120102474A1 (en) Static analysis of client-server applications using framework independent specifications
CN111143087A (zh) 一种接口调用方法、装置、存储介质和服务器
US9336014B2 (en) Method, apparatus, and system for human-machine interaction
CN110489310B (zh) 一种记录用户操作的方法、装置、存储介质及计算机设备
US20100306766A1 (en) Adding aspects to virtual machine monitors
US20130067439A1 (en) Injecting faults into program for testing
US20230401058A1 (en) Semantic functional wrappers of services
US10970055B2 (en) Identifying software and hardware bottlenecks
US20160150028A1 (en) Adapter for communication between web applications within a browser
US20160110170A1 (en) Message inlining
US9027152B2 (en) Device for right managing web data, recording medium for performing method for right managing web data on computer, and device and method for providing right management information
WO2021036987A1 (fr) Procédé et dispositif de réalisation d'exploitation et de surveillance de maintenance
CN107769974B (zh) 一种服务发布方法及装置
US20150205649A1 (en) Operating a Program Code Object in Conjunction with an Application Context
CN112925523A (zh) 对象比较方法、装置、设备及计算机可读介质
US10303580B2 (en) Controlling debug processing
US20190370039A1 (en) Methods for facilitating self-service automation utilities and devices thereof
CN111984427B (zh) 一种非侵入的Web系统互斥锁实现方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16843595

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16843595

Country of ref document: EP

Kind code of ref document: A1