Task processing method and device, computer equipment and storage medium

Abstract

The invention belongs to the technical field of data processing, and relates to a task processing method and device, computer equipment and a storage medium, and the method comprises the steps: obtaining a processing state of an uploaded task, and judging whether the processing state changes or not; if yes, obtaining a calling entrusting method corresponding to the multicast entrusting class; executing a call delegation method to traverse instances of all delegation wrappers contained in an internal set maintained by the multicast delegation class; detecting whether the entrusting objects packaged in all the entrusting packers are in a survival state or not; if yes, obtaining a target message corresponding to the processing state; and respectively transmitting the target message to each entrusting object to control each entrusting object to respectively carry out view updating processing corresponding to the uploading task. In addition, the target message may be stored in the blockchain. According to the invention, based on the use of the multicast entrusted processing mode, the coupling between the views and the uploading tasks is reduced, the problem of data synchronization is avoided, and the processing intelligence of the monitoring processing of the uploading tasks is effectively improved.

Description

Technical Field

[0001] The present application relates to the fields of data processing technology and financial technology, and in particular to task processing methods, devices, computer equipment and storage media. Background Art

[0002] In the software development process of financial enterprises, especially in applications involving multimedia content processing, such as video sharing platforms, online education platforms, or enterprise-level content management systems, the video file upload function is a core and frequently used service. These systems usually need to handle a large number of concurrent upload tasks while maintaining the real-time responsiveness and interactivity of the user interface to provide a smooth user experience.

[0003] Traditional upload task processing mechanisms often rely on the Delegate Pattern, which defines a one-to-one callback interface to allow one object (the delegator) to notify another object (the agent) when a specific event occurs and pass relevant information. In the video upload scenario, this usually means that the upload task class (the delegator) will directly notify the UI view (the agent) responsible for displaying this information of events such as progress updates and state changes.

[0004] However, as the complexity of applications and user needs grow, the traditional delegation model gradually reveals its limitations. In particular, in scenarios where multiple UI views need to monitor changes in the same upload task at the same time, the one-to-one delegation relationship is no longer applicable. At this point, if the traditional delegation model is continued, the upload task delegation will have to be set up separately for each view, which not only increases code redundancy and maintenance difficulty, but may also cause data synchronization problems and affect user experience. Summary of the invention

[0005] The purpose of the embodiments of the present application is to propose a task processing method, apparatus, computer equipment and storage medium to solve the technical problems that the delegation mode adopted by the existing upload task processor has code redundancy and high maintenance difficulty, and may cause data synchronization problems.

[0006] In order to solve the above technical problems, the present application provides a task processing method, which adopts the following technical solutions:

[0007] Obtaining the processing status of the upload task and determining whether the processing status has changed;

[0008] If so, obtain the call delegate method corresponding to the preset multicast delegate class;

[0009] Execute the calling delegate method to traverse all instances of delegate wrappers contained in the internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes multiple;

[0010] Check whether all the delegate objects encapsulated in the delegate wrappers are alive;

[0011] If so, obtaining a target message corresponding to the processing state;

[0012] The target message is delivered to each of the delegate objects respectively, so as to control each of the delegate objects to perform view update processing corresponding to the upload task respectively.

[0013] Furthermore, the step of detecting whether all the delegate objects encapsulated in the delegate wrappers are alive specifically includes:

[0014] Obtaining a first delegate object encapsulated in a specified delegate wrapper; wherein the specified delegate wrapper is any one of all the delegate wrappers;

[0015] Obtaining a designated forwarding method corresponding to the first delegate object;

[0016] Calling the specified forwarding method and determining whether the specified forwarding method is successfully called;

[0017] If the call is successful, it is determined that the first delegate object is in a live state; otherwise, it is determined that the first delegate object is not in a live state.

[0018] Furthermore, after the step of detecting whether all the delegate objects encapsulated in the delegate wrappers are alive, the method further includes:

[0019] If all the delegate objects encapsulated in the delegate wrappers are not in a survival state, obtaining survival state detection results corresponding to all the delegate objects;

[0020] Based on the survival status detection result, screening out a second delegate object in a survival state from all the delegate objects;

[0021] The target message is delivered to each of the second delegate objects respectively, so as to control each of the second delegate objects to perform view update processing corresponding to the upload task respectively.

[0022] Furthermore, after the step of obtaining the survival status detection results corresponding to all the delegate objects, the method further includes:

[0023] Based on the survival status detection result, screening out a third delegation object that is not in a survival status from all the delegation objects;

[0024] Determining a designated instance corresponding to the third delegate object from an internal set maintained by the multicast delegate class;

[0025] The designated instance is removed from the internal collection maintained by the multicast delegate class.

[0026] Furthermore, the task processing method further includes:

[0027] Determine whether a delegate object modification request triggered by a user is received; wherein the delegate object modification request carries delegate object information and modification type information;

[0028] If so, extracting the delegate object information and the modification type information from the delegate object modification request;

[0029] Obtaining a specified processing method corresponding to the modification type information;

[0030] The specified processing method is executed to perform a delegate object modification process corresponding to the delegate object information on the internal collection maintained by the multicast delegate class.

[0031] Furthermore, the delegation object modification request also carries user information of the user; and the step of extracting the delegation object information and the modification type information from the delegation object modification request specifically includes:

[0032] Extracting the user information from the delegate object modification request;

[0033] Acquire multiple designated biometric information corresponding to the user;

[0034] authenticating the user based on all of the specified biometric information;

[0035] If the user passes the identity authentication, the user is subject to a permission verification based on the user information and a preset permission verification model;

[0036] If the user passes the authority verification, the step of extracting the delegate object information and the modification type information from the delegate object modification request is performed.

[0037] Furthermore, the step of performing permission verification on the user based on the user information and a preset permission verification model specifically includes:

[0038] Calling the permission verification model, and acquiring a specified permission level corresponding to the user information based on the permission verification model;

[0039] Determining a designated processing operation corresponding to the delegate object modification request;

[0040] Calling a preset operation permission table, and querying the specified permission level range corresponding to the specified processing operation from the operation permission table;

[0041] Determining whether the specified permission level is within the specified permission level range;

[0042] If so, it is determined that the user has passed the authority verification; otherwise, it is determined that the user has not passed the authority verification.

[0043] In order to solve the above technical problems, the embodiment of the present application further provides a task processing device, which adopts the following technical solution:

[0044] The first judgment module is used to obtain the processing status of the upload task and judge whether the processing status has changed;

[0045] A first acquisition module, for acquiring a call delegate method corresponding to a preset multicast delegate class;

[0046] An execution module, used for executing the calling delegate method to traverse all instances of delegate wrappers contained in an internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes a plurality;

[0047] A detection module, used for detecting whether all the delegate objects encapsulated in the delegate wrappers are in a live state;

[0048] a second acquisition module, configured to, if yes, acquire a target message corresponding to the processing state;

[0049] The delivery module is used to deliver the target message to each of the delegate objects respectively, so as to control each of the delegate objects to perform view update processing corresponding to the upload task respectively.

[0050] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:

[0051] Obtaining the processing status of the upload task and determining whether the processing status has changed;

[0052] If so, obtain the call delegate method corresponding to the preset multicast delegate class;

[0053] Execute the calling delegate method to traverse all instances of delegate wrappers contained in the internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes multiple;

[0054] Check whether all the delegate objects encapsulated in the delegate wrappers are alive;

[0055] If so, obtaining a target message corresponding to the processing state;

[0056] The target message is delivered to each of the delegate objects respectively, so as to control each of the delegate objects to perform view update processing corresponding to the upload task respectively.

[0057] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:

[0058] Obtaining the processing status of the upload task and determining whether the processing status has changed;

[0059] If so, obtain the call delegate method corresponding to the preset multicast delegate class;

[0060] Execute the calling delegate method to traverse all instances of delegate wrappers contained in the internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes multiple;

[0061] Check whether all the delegate objects encapsulated in the delegate wrappers are alive;

[0062] If so, obtaining a target message corresponding to the processing state;

[0063] The target message is delivered to each of the delegate objects respectively, so as to control each of the delegate objects to perform view update processing corresponding to the upload task respectively.

[0064] Compared with the prior art, the embodiments of the present application have the following beneficial effects:

[0065] The present application first obtains the processing status of the upload task and determines whether the processing status has changed; if so, obtains the call delegate method corresponding to the preset multicast delegate class; then executes the call delegate method to traverse all instances of delegate wrappers contained in the internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes multiple; subsequently detects whether all the delegate objects encapsulated in the delegate wrappers are in a survival state; if so, obtains the target message corresponding to the processing status; finally, passes the target message to each of the delegate objects respectively to control each of the delegate objects to perform view update processing corresponding to the upload task respectively. When the present application detects that the processing status of the upload task has changed, it will intelligently obtain and execute the call delegate method corresponding to the multicast delegate class to traverse all instances of the delegate wrapper contained in the internal collection maintained by the multicast delegate class, and when it detects that all the delegate objects encapsulated in the delegate wrapper are alive, it will automatically obtain the target message corresponding to the processing status, and pass the target message to each of the delegate objects to control each of the delegate objects to perform view update processing corresponding to the upload task, thereby automatically and intelligently constructing a multicast delegate processing mode that supports one-to-many relationships, which can monitor and display the status changes of the upload task in multiple views. This processing mode not only improves the flexibility and maintainability of the code, but also helps to reduce the coupling between the view and the upload task, avoid data synchronization problems, and effectively improve the processing intelligence of the monitoring processing of the upload task. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0067] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0068] Figure 2 A flowchart of an embodiment of a task processing method according to the present application;

[0069] Figure 3 is a structural schematic diagram of an embodiment of a task processing device according to the present application;

[0070] Figure 4 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0071] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by technicians in the technical field of the present application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application; the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0072] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0073] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0074] like Figure 1 As shown, the system architecture 100 may include a terminal device 101, a network 102 and a server 103. The terminal device 101 may be a laptop 1011, a tablet computer 1012 or a mobile phone 1013. The network 102 is used to provide a medium for a communication link between the terminal device 101 and the server 103. The network 102 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0075] The user can use the terminal device 101 to interact with the server 103 through the network 102 to receive or send messages, etc. Various communication client applications can be installed on the terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0076] The terminal device 101 can be any electronic device with a display screen and supporting web browsing. In addition to the laptop computer 1011, tablet computer 1012 or mobile phone 1013, the terminal device 101 can also be an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 (Moving Picture Experts Group Audio Layer IV), a laptop computer, a desktop computer, etc.

[0077] The server 103 may be a server that provides various services, such as a background server that provides support for a web page displayed on the terminal device 101 .

[0078] It should be noted that the task processing method provided in the embodiment of the present application is generally executed by a server / terminal device, and accordingly, the task processing device is generally arranged in the server / terminal device.

[0079] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0080] Continue to refer Figure 2 , shows a flow chart of an embodiment of the task processing method according to the present application. According to different requirements, the order of the steps in the flow chart can be changed, and some steps can be omitted. The task processing method provided in the embodiment of the present application can be applied to any scenario where task processing is required, and the task processing method can be applied to products in these scenarios, for example, task processing in the financial insurance field. The task processing method comprises the following steps:

[0081] Step S201, obtaining the processing status of the upload task, and determining whether the processing status has changed.

[0082] In this embodiment, the task processing method is executed on the electronic device (eg Figure 1The server / terminal device shown in the figure) can obtain the processing status of the upload task through a wired connection or a wireless connection. It should be pointed out that the above-mentioned wireless connection method may include but is not limited to 3G / 4G / 5G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other wireless connection methods currently known or to be developed in the future. The executor of the present application may be a task processing system, or simply referred to as a system. The present application can be applied to the monitoring and processing scenarios of upload tasks related to picture files or video files related to insurance business in the financial field. Among them, the changes in the processing status of the above-mentioned upload task may include starting to upload, progress update, upload completion or the above-mentioned failure.

[0083] Step S202: If yes, obtain the calling delegate method corresponding to the preset multicast delegate class.

[0084] In this embodiment, if it is detected that the processing status of the upload task has changed, the call delegate method corresponding to the preset multicast delegate class is obtained. Specifically, a multicast delegate class (MulticastDelegate) is pre-defined. This multicast delegate class is a generic class that allows a protocol type (ProtocolType) to be specified as a parameter. This protocol type will define the method that the delegate needs to follow. A container (such as a collection) will be used inside the multicast delegate to store delegate wrappers (DelegateWrapper), which hold weak references to the actual delegate object. Among them, an internal class DelegateWrapper is defined in the MulticastDelegate class to wrap the delegate object as a weak attribute to ensure that the delegate object is a weak reference. In this way, the multicast delegate can hold a strong wrapper instance instead of directly holding the delegate, thereby avoiding circular references and memory leaks. In addition, DelegateWrapper holds a weak reference to an object that implements ProtocolType and provides a method to safely call the object's method (if the object is still alive).

[0085] And multicast delegates allow a delegate object to hold references to multiple target methods, that is, multiple callback functions can be added to the delegate. Multicast delegates are often used in event processing scenarios, and can trigger multiple registered callback functions in one call, making event broadcasting more convenient and simple. Multicast delegates call target methods in the order they are added, ensuring that the calling order of callback functions is controllable.

[0086] In addition, the above-mentioned calling delegate method is specifically the invokeDelegate() method, which is responsible for actually calling all delegate objects. This method will be called when all registered delegate objects need to be notified. It will traverse all DelegateWrapper instances and try to safely call the methods of the objects they wrap (if the objects are still alive). By calling the invokeDelegate() method of the multicast delegate, all registered views (delegate objects) are notified to update the display accordingly.

[0087] Step S203, executing the calling delegate method to traverse all instances of delegate wrappers contained in the internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes multiple.

[0088] In this embodiment, by executing the above-mentioned calling delegate method, the method will automatically traverse all instances of the delegate wrappers contained in the internal collection maintained by the multicast delegate class.

[0089] Step S204: Detect whether all the delegate objects encapsulated in the delegate wrapper are in a live state.

[0090] In this embodiment, the specific implementation process of the above-mentioned detection of whether all the delegate objects encapsulated in the delegate wrappers are in a live state will be further described in detail in subsequent specific embodiments of the present application, and will not be elaborated on here.

[0091] Step S205: If yes, obtain the target message corresponding to the processing status.

[0092] In this embodiment, the above-mentioned target message refers to a pre-built specific delegate method corresponding to the processing status. Specifically, if the processing status is to start uploading, the corresponding target message is uploadDidStart, which is used to notify all listeners that the upload has started. If the processing status is to update the upload progress, the corresponding target message is uploadProgressUpdated, and the delegate method accepts a parameter representing the progress (such as the progress percentage of the Float type). If the processing status is that the upload is completed, the corresponding target message is uploadDidComplete, to notify all listeners that the upload has been completed. If the processing status is that the upload fails, the corresponding target message is uploadDidFail, and the delegate method accepts a parameter of type Error.

[0093] Step S206: delivering the target message to each of the delegate objects respectively, so as to control each of the delegate objects to perform view update processing corresponding to the upload task respectively.

[0094] In this embodiment, the target message is passed to each delegate object in the live state, and each delegate object is controlled to perform view update processing corresponding to the upload task, thereby automatically notifying all registered views (delegate objects) to perform corresponding update display. Specifically, the view (delegate object) should implement the method defined in ProtocolType, and update its UI in this method to reflect the latest status of the upload task, thereby completing the view update processing for the upload task.

[0095] The present application first obtains the processing status of the upload task and determines whether the processing status has changed; if so, obtains the call delegate method corresponding to the preset multicast delegate class; then executes the call delegate method to traverse all instances of delegate wrappers contained in the internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes multiple; subsequently detects whether all the delegate objects encapsulated in the delegate wrappers are in a survival state; if so, obtains the target message corresponding to the processing status; finally, passes the target message to each of the delegate objects respectively to control each of the delegate objects to perform view update processing corresponding to the upload task respectively. When the present application detects that the processing status of the upload task has changed, it will intelligently obtain and execute the call delegate method corresponding to the multicast delegate class to traverse all instances of the delegate wrapper contained in the internal collection maintained by the multicast delegate class, and when it detects that all the delegate objects encapsulated in the delegate wrapper are alive, it will automatically obtain the target message corresponding to the processing status, and pass the target message to each of the delegate objects to control each of the delegate objects to perform view update processing corresponding to the upload task, thereby automatically and intelligently constructing a multicast delegate processing mode that supports one-to-many relationships, which can monitor and display the status changes of the upload task in multiple views. This processing mode not only improves the flexibility and maintainability of the code, but also helps to reduce the coupling between the view and the upload task, avoid data synchronization problems, and effectively improve the processing intelligence of the monitoring processing of the upload task.

[0096] In some optional implementations, step S204 includes the following steps:

[0097] Gets the first delegate object encapsulated in the specified delegate wrapper.

[0098] In this embodiment, the designated delegation wrapper is any one of all the delegation wrappers. The first delegation object is the delegation object encapsulated in the designated delegation wrapper.

[0099] Obtain a specified forwarding method corresponding to the first delegate object.

[0100] In this embodiment, the designated forwarding method is a method for detecting whether the first delegate object is still alive, and specifically may be an invokeIfAlive() method.

[0101] The specified forwarding method is called, and it is determined whether the specified forwarding method is called successfully.

[0102] In this embodiment, the above-mentioned designated forwarding method is attempted to be safely called and a corresponding calling result is obtained, wherein the calling result includes a calling success or a calling failure.

[0103] If the call is successful, it is determined that the first delegate object is in a live state; otherwise, it is determined that the first delegate object is not in a live state.

[0104] In this embodiment, if the designated forwarding method is successfully called, the first delegate object is determined to be alive, and if the designated forwarding method is unsuccessful, the first delegate object is determined to be not alive.

[0105] The present application obtains the first delegate object encapsulated in the designated delegate wrapper; wherein the designated delegate wrapper is any one of all the delegate wrappers; then obtains the designated forwarding method corresponding to the first delegate object; subsequently calls the designated forwarding method and determines whether the designated forwarding method is successfully called; if the call is successful, the first delegate object is determined to be alive, otherwise the first delegate object is determined to be not alive. The present application obtains the first delegate object encapsulated in the designated delegate wrapper, and then based on the use of the designated forwarding method corresponding to the first delegate object, calls the designated forwarding method to obtain the corresponding call result, and then analyzes the call result, so as to realize the rapid and accurate generation of the survival status detection result corresponding to the delegate object, thereby improving the processing efficiency of the survival status detection and ensuring the data accuracy of the obtained survival status detection result.

[0106] In some optional implementations of this embodiment, after step S204, the electronic device may further perform the following steps:

[0107] If all the delegate objects encapsulated in the delegate wrappers are not in a survival state, then the survival state detection results corresponding to all the delegate objects are obtained.

[0108] In this embodiment, the survival state detection process can be performed on each of the delegate objects encapsulated in the delegate wrapper to obtain the survival state detection results corresponding to all the delegate objects. The survival state detection results include survival state (i.e., non-null and not released) or non-survival state.

[0109] Based on the survival status detection result, a second delegation object in a survival state is screened out from all the delegation objects.

[0110] In this embodiment, by performing content analysis and statistical processing on the above survival status detection result, the second delegate object in the survival status can be screened out from all the delegate objects.

[0111] The target message is delivered to each of the second delegate objects respectively, so as to control each of the second delegate objects to perform view update processing corresponding to the upload task respectively.

[0112] In this embodiment, the target message is passed to each of the second delegate objects to control each of the second delegate objects to perform the view update processing corresponding to the upload task. The specific implementation process of passing the target message to each of the delegate objects to control each of the delegate objects to perform the view update processing corresponding to the upload task can be referred to above, and will not be described in detail here. If the delegate object does not exist in the delegate wrapper, the call of the delegate object is skipped and the next delegate object is processed.

[0113] If the present application detects that all the delegate objects encapsulated in the delegate wrappers are not all alive, then the survival status detection results corresponding to all the delegate objects are obtained; then based on the survival status detection results, the second delegate object in the survival state is screened out from all the delegate objects; and the target message is subsequently delivered to each of the second delegate objects respectively to control each of the second delegate objects to perform the view update processing corresponding to the upload task respectively. If the present application detects that all the delegate objects encapsulated in the delegate wrappers are not all alive, the second delegate object in the survival state is intelligently screened out from all the delegate objects according to the obtained survival status detection results corresponding to all the delegate objects, so that only the target message will be delivered to each of the second delegate objects respectively to control each of the second delegate objects to perform the view update processing corresponding to the upload task respectively, and the target message will not be delivered to the invalid delegate objects in the survival state encapsulated in the delegate wrapper, thereby achieving safe calling of the second delegate object and effectively improving the processing accuracy of the view update processing corresponding to the upload task.

[0114] In some optional implementations, after the step of obtaining the survival status detection results corresponding to all the delegate objects, the electronic device may further perform the following steps:

[0115] Based on the survival status detection result, a third delegation object that is not in a survival status is screened out from all the delegation objects.

[0116] In this embodiment, the content of the survival status detection result includes survival status or non-survival status. The survival status detection result can be subjected to content analysis and statistical processing, so as to filter out the third delegate object that is not in the survival status from all the delegate objects.

[0117] A designated instance corresponding to the third delegate object is determined from an internal collection maintained by the multicast delegate class.

[0118] In this embodiment, the third delegate object may be used to perform data query on the internal collection maintained by the multicast delegate class to determine the designated instance corresponding to the third delegate object.

[0119] The designated instance is removed from the internal collection maintained by the multicast delegate class.

[0120] In this embodiment, the removeDelegate method can be used to remove the specified instance from the internal collection maintained by the multicast delegate class.

[0121] The present application selects the third delegate object that is not in a survival state from all the delegate objects based on the survival state detection result; then determines the specified instance corresponding to the third delegate object from the internal collection maintained by the multicast delegate class; and subsequently removes the specified instance from the internal collection maintained by the multicast delegate class. When the present application detects that all the delegate objects encapsulated in the delegate wrapper are not in a survival state, it intelligently selects the third delegate object that is not in a survival state from all the delegate objects based on the survival state detection result corresponding to all the delegate objects, and then determines the specified instance corresponding to the third delegate object from the internal collection maintained by the multicast delegate class and performs corresponding removal processing, so as to automatically complete the deregistration of the third delegate object that does not need to monitor the upload task from the internal collection maintained by the multicast delegate class, so as to avoid memory leaks, and effectively realize the automatic update processing of the delegate objects in the internal collection maintained by the multicast delegate class.

[0122] In some optional implementations, the electronic device may further perform the following steps:

[0123] Determine whether a delegation object modification request triggered by a user is received; wherein the delegation object modification request carries delegation object information and modification type information.

[0124] In this embodiment, the above-mentioned delegate object modification request is a request triggered by a user for modifying all delegate wrappers contained in the internal collection maintained by the multicast delegate class based on personal needs. The above-mentioned delegate object information may refer to the information of the instance of the delegate object that needs to be modified. The above-mentioned modification type information may include an addition type or a removal type.

[0125] If so, extract the delegate object information and the modification type information from the delegate object modification request.

[0126] In this embodiment, the corresponding entrustment object information and modification type information can be extracted by performing information parsing on the entrustment object modification request.

[0127] Obtain a specified processing method corresponding to the modification type information.

[0128] In this embodiment, processing methods corresponding to different modification type information are pre-set. Among them, the processing methods include an addition processing method corresponding to the addition type, and a removal processing method corresponding to the removal type. The above-mentioned addition processing method is specifically addDeleagte, and addDeleagte can be used to add a new delegate object to the multicast delegate class. This method will create a new DelegateWrapper instance, wrap the delegate object as a weak reference, and add it to the internal collection maintained by the multicast delegate class. The above-mentioned removal processing method is specifically removeDelegate. RemoveDelegate can be used to remove a delegate object from the multicast delegate class. This method will traverse the internal collection maintained by the multicast delegate class, find and remove the DelegateWrapper instance corresponding to the given delegate object.

[0129] The specified processing method is executed to perform a delegate object modification process corresponding to the delegate object information on the internal collection maintained by the multicast delegate class.

[0130] In this embodiment, by executing the above-mentioned specified processing method, it is possible to automatically and accurately perform delegation object modification processing corresponding to the delegation object information on the internal collection maintained by the multicast delegation class, for example, including the processing of adding delegation objects or removing delegation objects.

[0131] The present application determines whether a user-triggered delegation object modification request is received; wherein the delegation object modification request carries delegation object information and modification type information; if so, extracts the delegation object information and the modification type information from the delegation object modification request; then obtains a specified processing method corresponding to the modification type information; and subsequently executes the specified processing method to perform delegation object modification processing corresponding to the delegation object information on the internal collection maintained by the multicast delegation class. After receiving a user-triggered delegation object modification request, the present application automatically extracts the delegation object information and the modification type information from the delegation object modification request, and then automatically and accurately performs delegation object modification processing corresponding to the delegation object information on the internal collection maintained by the multicast delegation class by executing the specified processing method corresponding to the modification type information, so as to realize the corresponding delegation object modification processing on the internal collection maintained by the multicast delegation class based on the delegation object information and modification type information input by the user, thereby improving the processing intelligence and accuracy of delegation object modification, and is conducive to improving the user experience.

[0132] In some optional implementations of this embodiment, the delegation object modification request further carries user information of the user; and extracting the delegation object information and the modification type information from the delegation object modification request comprises the following steps:

[0133] The user information is extracted from the delegate object modification request.

[0134] In this embodiment, the corresponding user information can be extracted by parsing the above-mentioned delegation object modification request, wherein the user information may include the user's name.

[0135] Acquire a plurality of designated biometric information corresponding to the user.

[0136] In this embodiment, the number of the specified biometric information to be obtained is not specifically limited, and can be randomly set according to actual business usage requirements. Exemplarily, the specified biometric information can include any of fingerprints, faces, irises, eyebrows, lips, etc.

[0137] The user is authenticated based on all of the specified biometric information.

[0138] In this embodiment, all biometric information corresponding to the user information can be first obtained from a pre-constructed feature database, and then based on the feature types corresponding to the above-mentioned multiple specified biometric information, the target biometric information matching the feature type is screened out from all the biometric information. Then, the above-mentioned specified biometric information is respectively verified one by one by using the above-mentioned target biometric information. Specifically, if the specified biometric information includes facial feature information and eyebrow feature information, the target biometric information includes standard facial feature information and standard eyebrow feature information. Then, the above-mentioned facial feature information is used to perform a similarity comparison with the corresponding standard facial feature information, and the above-mentioned eyebrow feature information is used to perform a similarity comparison with the corresponding standard eyebrow feature information. If all the calculated similarities are greater than the preset similarity threshold, it is determined that the specified biometric information has passed the verification, and then it is determined that the user has passed the identity authentication. If there is a situation where all the calculated similarities are less than the corresponding similarity threshold, it is determined that the specified biometric information has not passed the verification, and then it is determined that the user has not passed the identity authentication. The value of the similarity threshold is not specifically limited and can be set according to actual business requirements, for example, 0.91. In addition, if the user fails identity authentication, the user is determined not to be a legitimate user, and the request to modify the delegated object is directly rejected.

[0139] If the user passes the identity authentication, the user's authority is verified based on the user information and a preset authority verification model.

[0140] In this embodiment, the specific implementation process of the above-mentioned permission verification of the user based on the user information and the preset permission verification model will be further described in detail in the subsequent specific embodiments of this application, and will not be elaborated in detail here.

[0141] If the user passes the authority verification, the step of extracting the delegate object information and the modification type information from the delegate object modification request is performed.

[0142] In this embodiment, if the user passes the authority check, it is determined that the user has the authority to perform the delegated object modification operation, and then the delegated object modification request is responded to and the corresponding subsequent processing flow is executed.

[0143] The present application extracts the user information from the delegated object modification request; then obtains multiple specified biometric information corresponding to the user; then authenticates the user based on all the specified biometric information; if the user passes the identity authentication, then the user is subsequently authenticated based on the user information and a preset permission verification model; if the user passes the permission verification, the step of extracting the delegated object information and the modification type information from the delegated object modification request is performed. When the present application receives a delegated object modification request triggered by a user, it will also intelligently extract the user information from the delegated object modification request, and obtain multiple specified biometric information corresponding to the user, and then authenticate the user based on the use of the specified biometric information, and authenticate the user based on the use of the permission verification model. Only when it is detected that the user has passed the identity authentication and permission verification, will the delegated object modification request be responded to and processed later, which effectively improves the standardized processing and security processing of delegated object modification requests, and ensures the security of responses to delegated object modification requests.

[0144] In some optional implementations of this embodiment, the performing permission verification on the user based on the user information and a preset permission verification model includes the following steps:

[0145] The permission verification model is called, and a specified permission level corresponding to the user information is obtained based on the permission verification model.

[0146] In this embodiment, the permission verification model is a pre-built big data model that stores a one-to-one mapping relationship between the name information of each staff member in the enterprise and the permission level. The permission verification model can be queried using the user information to obtain the specified permission level corresponding to the user information.

[0147] A specified processing operation corresponding to the delegate object modification request is determined.

[0148] In this embodiment, for each processing operation, a processing operation identifier matching the processing operation is pre-set, and the processing operation identifier is unique, and one processing operation corresponds to one processing operation identifier. The designated processing operation identifier corresponding to the above-mentioned delegate object modification request can be obtained, and then the matching designated processing operation can be queried according to the designated processing operation identifier.

[0149] A preset operation permission table is called, and a designated permission level range corresponding to the designated processing operation is queried from the operation permission table.

[0150] In this embodiment, the operation permission table is a pre-constructed data table storing a variety of processing operation identifiers and permission level ranges corresponding to the various processing operation identifiers. Specifically, the specified business operation identifier corresponding to the specified processing operation can be obtained, and then the specified business operation identifier can be used to query the operation permission table to obtain the specified permission level range corresponding to the specified processing operation.

[0151] Determine whether the specified permission level is within the specified permission level range.

[0152] In this embodiment, the specified permission level can be compared with the two endpoint values ​​included in the above-mentioned specified permission level range to obtain a corresponding numerical comparison result, and based on the numerical comparison result, it can be identified whether the specified permission level is within the specified permission level range.

[0153] If so, it is determined that the user has passed the authority verification; otherwise, it is determined that the user has not passed the authority verification.

[0154] In this embodiment, if the specified permission level is within the specified permission level range, it indicates that the user has the permission to perform the delegated object modification operation corresponding to the delegated object modification request, and the user is determined to have passed the permission check. If the specified permission level is not within the specified permission level range, it indicates that the user does not have the permission to perform the delegated object modification operation corresponding to the delegated object modification request, and the user is determined to have failed the permission check.

[0155] The present application calls the permission verification model, and obtains the designated permission level corresponding to the user information based on the permission verification model; then determines the designated processing operation corresponding to the delegated object modification request; then calls the preset operation permission table, and queries the designated permission level range corresponding to the designated processing operation from the operation permission table; subsequently determines whether the designated permission level is within the designated permission level range. Only when it is detected that the designated permission level is within the designated permission level range, it indicates that the user has the permission to perform the delegated object modification operation corresponding to the above-mentioned delegated object modification request, thereby determining that the user has passed the permission verification, effectively improving the processing intelligence and processing accuracy of the user's permission verification, and ensuring the accuracy of the obtained user's permission verification result. In addition, only after it is determined that the user has passed the permission verification, will the delegated object modification request be responded to and processed later, effectively improving the standardized processing and security processing of the delegated object modification request, and ensuring the security of the response to the delegated object modification request.

[0156] In some optional implementations, the user information obtained is subject to the user's consent and complies with relevant laws and policies.

[0157] In addition, the non-Company software tools or components that appear in the embodiments of the present application are merely examples and do not represent actual use.

[0158] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0159] It should be emphasized that in order to further ensure the privacy and security of the above-mentioned target message, the above-mentioned target message can also be stored in a node of a blockchain.

[0160] The blockchain referred to in this application is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer.

[0161] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Among them, artificial intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0162] AI basic technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, mechatronics, etc. AI software technologies mainly include computer vision technology, robotics technology, biometrics technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0163] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0164] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0165] Further references Figure 3 , as a response to the above Figure 2 The present application provides an embodiment of a task processing device, and the device embodiment is similar to Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0166] like Figure 3 As shown, the task processing device 300 described in this embodiment includes: a first judgment module 301, a first acquisition module 302, an execution module 303, a detection module 304, a second acquisition module 305 and a transmission module 306. Among them:

[0167] The first judgment module 301 is used to obtain the processing status of the upload task and judge whether the processing status has changed;

[0168] A first acquisition module 302 is used to acquire a call delegation method corresponding to a preset multicast delegation class;

[0169] An execution module 303 is used to execute the calling delegate method to traverse all instances of delegate wrappers contained in the internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes multiple;

[0170] A detection module 304 is used to detect whether all the delegate objects encapsulated in the delegate wrapper are in a live state;

[0171] A second acquisition module 305 is used to acquire a target message corresponding to the processing state;

[0172] The delivery module 306 is used to deliver the target message to each of the delegate objects respectively, so as to control each of the delegate objects to perform view update processing corresponding to the upload task respectively.

[0173] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task processing method in the above-mentioned implementation mode, and are not described in detail here.

[0174] In some optional implementations of this embodiment, the detection module 304 includes:

[0175] A first acquisition submodule is used to acquire a first delegate object encapsulated in a specified delegate wrapper; wherein the specified delegate wrapper is any one of all the delegate wrappers;

[0176] A second acquisition submodule, used to acquire a designated forwarding method corresponding to the first delegate object;

[0177] A judgment submodule, used to call the specified forwarding method and judge whether the specified forwarding method is successfully called;

[0178] The determination submodule is used to determine that the first delegate object is alive if the call is successful, otherwise, determine that the first delegate object is not alive.

[0179] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task processing method in the above-mentioned implementation mode, and are not described in detail here.

[0180] In some optional implementations of this embodiment, the task processing device further includes:

[0181] A third acquisition module is used for acquiring survival status detection results corresponding to all the delegate objects if all the delegate objects encapsulated in the delegate wrappers are not in survival status;

[0182] A first screening module, configured to screen out a second delegate object in a live state from all the delegate objects based on the live state detection result;

[0183] The control module is used to transmit the target message to each of the second delegate objects respectively, so as to control each of the second delegate objects to perform view update processing corresponding to the upload task respectively.

[0184] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task processing method in the above-mentioned implementation mode, and are not described in detail here.

[0185] In some optional implementations of this embodiment, the task processing device further includes:

[0186] A second screening module, configured to screen out a third delegate object that is not in a survival state from all the delegate objects based on the survival state detection result;

[0187] a determination module, configured to determine a designated instance corresponding to the third delegate object from an internal set maintained by the multicast delegate class;

[0188] The removal module is used to remove the specified instance from the internal collection maintained by the multicast delegation class.

[0189] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task processing method in the above-mentioned implementation mode, and are not described in detail here.

[0190] In some optional implementations of this embodiment, the task processing device further includes:

[0191] A second judgment module is used to judge whether a delegation object modification request triggered by a user is received; wherein the delegation object modification request carries delegation object information and modification type information;

[0192] An extraction module, configured to extract the delegate object information and the modification type information from the delegate object modification request;

[0193] A fourth acquisition module, used to acquire a specified processing method corresponding to the modification type information;

[0194] The modification module is used to execute the specified processing method to perform a delegation object modification process corresponding to the delegation object information on the internal collection maintained by the multicast delegation class.

[0195] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task processing method in the above-mentioned implementation mode, and are not described in detail here.

[0196] In some optional implementations of this embodiment, the extraction module includes:

[0197] An extraction submodule, used for extracting the user information from the delegate object modification request;

[0198] A third acquisition submodule is used to acquire a plurality of designated biometric feature information corresponding to the user;

[0199] A verification submodule, configured to authenticate the user based on all the specified biometric information;

[0200] A verification submodule, configured to perform a permission verification on the user based on the user information and a preset permission verification model if the user passes identity authentication;

[0201] The execution submodule is used to execute the step of extracting the delegate object information and the modification type information from the delegate object modification request if the user passes the authority verification.

[0202] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task processing method in the above-mentioned implementation mode, and are not described in detail here.

[0203] In some optional implementations of this embodiment, the check submodule includes:

[0204] A calling unit, configured to call the permission verification model and obtain a specified permission level corresponding to the user information based on the permission verification model;

[0205] A determination unit, configured to determine a designated processing operation corresponding to the delegate object modification request;

[0206] A query unit, used to call a preset operation permission table, and query the specified permission level range corresponding to the specified processing operation from the operation permission table;

[0207] A judging unit, used to judge whether the specified permission level is within the specified permission level range;

[0208] The determination unit is used to determine that if yes, the user has passed the authority verification, otherwise, determine that the user has not passed the authority verification.

[0209] In this embodiment, the operations performed by the above modules or units correspond one-to-one to the steps of the task processing method in the above-mentioned implementation mode, and are not described in detail here.

[0210] To solve the above technical problems, the present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0211] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 4 with components 41-43, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0212] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.

[0213] The memory 41 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 41 can be an internal storage unit of the computer device 4, such as a hard disk or memory of the computer device 4. In other embodiments, the memory 41 can also be an external storage device of the computer device 4, such as a plug-in hard disk equipped on the computer device 4, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (FlashCard), etc. Of course, the memory 41 can also include both the internal storage unit of the computer device 4 and its external storage device. In this embodiment, the memory 41 is generally used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions of the task processing method, etc. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or are to be output.

[0214] The processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to run computer-readable instructions stored in the memory 41 or process data, such as computer-readable instructions for running the task processing method.

[0215] The network interface 43 may include a wireless network interface or a wired network interface. The network interface 43 is generally used to establish a communication connection between the computer device 4 and other electronic devices.

[0216] The present application also provides another implementation, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the task processing method as described above.

[0217] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0218] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.

Claims

1. A task processing method, characterized in that: The steps include: Obtaining the processing status of the upload task and determining whether the processing status has changed; If so, obtain the call delegate method corresponding to the preset multicast delegate class; Execute the calling delegate method to traverse all instances of delegate wrappers contained in the internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes multiple; Check whether all the delegate objects encapsulated in the delegate wrappers are alive; If so, obtaining a target message corresponding to the processing state; The target message is delivered to each of the delegate objects respectively, so as to control each of the delegate objects to perform view update processing corresponding to the upload task respectively.

2. The task processing method according to claim 1, characterized in that: The step of detecting whether all the delegate objects encapsulated in the delegate wrappers are in a live state specifically includes: Obtaining a first delegate object encapsulated in a specified delegate wrapper; wherein the specified delegate wrapper is any one of all the delegate wrappers; Obtaining a designated forwarding method corresponding to the first delegate object; Calling the specified forwarding method and determining whether the specified forwarding method is successfully called; If the call is successful, it is determined that the first delegate object is in a live state; otherwise, it is determined that the first delegate object is not in a live state.

3. The task processing method according to claim 1, characterized in that: After the step of detecting whether all the delegate objects encapsulated in the delegate wrappers are in a live state, the method further includes: If all the delegate objects encapsulated in the delegate wrappers are not in a survival state, obtaining survival state detection results corresponding to all the delegate objects; Based on the survival status detection result, screening out a second delegate object in a survival state from all the delegate objects; The target message is delivered to each of the second delegate objects respectively, so as to control each of the second delegate objects to perform view update processing corresponding to the upload task respectively.

4. The task processing method according to claim 3, characterized in that: After the step of obtaining the survival status detection results corresponding to all the delegate objects, the method further includes: Based on the survival status detection result, screening out a third delegation object that is not in a survival status from all the delegation objects; Determining a designated instance corresponding to the third delegate object from an internal set maintained by the multicast delegate class; The designated instance is removed from the internal collection maintained by the multicast delegate class.

5. The task processing method according to claim 1, characterized in that: The task processing method further includes: Determine whether a delegate object modification request triggered by a user is received; wherein the delegate object modification request carries delegate object information and modification type information; If so, extracting the delegate object information and the modification type information from the delegate object modification request; Obtaining a specified processing method corresponding to the modification type information; The specified processing method is executed to perform a delegate object modification process corresponding to the delegate object information on the internal collection maintained by the multicast delegate class.

6. The task processing method according to claim 5, characterized in that: The delegate object modification request also carries the user information of the user; The step of extracting the delegate object information and the modification type information from the delegate object modification request specifically includes: Extracting the user information from the delegate object modification request; Acquire multiple designated biometric information corresponding to the user; authenticating the user based on all of the specified biometric information; If the user passes the identity authentication, the user is subject to a permission verification based on the user information and a preset permission verification model; If the user passes the authority verification, the step of extracting the delegate object information and the modification type information from the delegate object modification request is performed.

7. The task processing method according to claim 6, characterized in that: The step of performing permission verification on the user based on the user information and a preset permission verification model specifically includes: Calling the permission verification model, and acquiring a specified permission level corresponding to the user information based on the permission verification model; Determining a designated processing operation corresponding to the delegate object modification request; Calling a preset operation permission table, and querying the specified permission level range corresponding to the specified processing operation from the operation permission table; Determining whether the specified permission level is within the specified permission level range; If so, it is determined that the user has passed the authority verification; otherwise, it is determined that the user has not passed the authority verification.

8. A task processing device, characterized in that: include: The first judgment module is used to obtain the processing status of the upload task and judge whether the processing status has changed; A first acquisition module, for acquiring a call delegate method corresponding to a preset multicast delegate class; An execution module, used for executing the calling delegate method to traverse all instances of delegate wrappers contained in an internal collection maintained by the multicast delegate class; wherein the number of the delegate wrappers includes a plurality; A detection module, used for detecting whether all the delegate objects encapsulated in the delegate wrappers are in a live state; a second acquisition module, configured to, if yes, acquire a target message corresponding to the processing state; The delivery module is used to deliver the target message to each of the delegate objects respectively, so as to control each of the delegate objects to perform view update processing corresponding to the upload task respectively.

9. A computer device, characterized in that: The method comprises a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the task processing method according to any one of claims 1 to 7 when executing the computer-readable instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the steps of the task processing method according to any one of claims 1 to 7 are implemented.

Images