Method and system for quickly shielding client fault based on instrumentation mode

Abstract

The invention discloses a method and a system for quickly shielding a client fault based on an instrumentation mode, and relates to the field of client fault processing. The method comprises the following steps of inserting a functional instrumentation point used for controlling a function and a function instrumentation point used for controlling a function into a client; generating functional configuration information by a server according to a fault occurrence function, and generating function configuration information according to a fault occurrence function; when the client is started, automatically obtaining the generated functional configuration information and function configuration information from the server; when the functional configuration information is queried by the client, disabling a corresponding function; and if the function configuration information is queried by the client, when the client performs execution operation at the function instrumentation point corresponding to the function configuration information, disabling a corresponding function, and skipping the function and continuing to execute other functions by the client. According to the method, a new function of the client can be quickly disabled and a fault caused by the new function is shielded, so that normal use of the client is ensured.

Description

technical field [0001] The invention relates to the field of client fault processing, in particular to a method and system for quickly shielding client faults based on stub insertion. Background technique [0002] The software development process of the CS (Client / Server, client / server) architecture is usually an iterative update process, and each iteration and update process will more or less introduce some new functions or new features. Although these new functions and features have been tested in detail before the version is released, there are still some unknown bugs that cannot be avoided after the release. Bugs are used to refer to potential faults that will occur during runtime in the client program or error. [0003] When a bug occurs on the client side, generally the problem of the bug file can only be modified by upgrading the client side. However, the cost of fixing bugs by upgrading the client is relatively high, and the time period is long, because it is impos...

AI Technical Summary

Problems solved by technology

However, the cost of fixing bugs by upgrading the client is relatively high, and the time period is long, because it is impossible to update the entire client because of a bug. Usually, it is updated uniformly after multiple bug feedbacks

If the client is just a small bug, but the consequences are more serious, there are often few modifications at this time, but it is a very complicated process to update the client. Although this design scheme is It can solve the problem, but the time cost, user traffic and other costs will be greatly increased

Images