Applet thread model and component invoking method based on same

Abstract

The invention provides an Applet thread model and a component invoking method based on the same. By utilizing a special double wall technology of components, the invocations of interface methods of component objects which aim at Applets and have Applet properties are all intercepted in the double wall, then invoking parameters and invoked interface method information are together packaged, and an invoked event is delivered into a message queue of an invoked Applet through a mechanism of delivering callback events; at the moment, an invoking thread enters a waiting state, and when a message cycle of the invoked Applet processes the invoked event, an Applet callback thread is used for executing a target interface method; after the execution is finished, a result is returned to the invoking thread waiting at the double wall; and then the result is returned to the Applet of an invoking party so as to finish an invocation. By utilizing the invention, the problem of multi-thread of Applets during mutually invoking is solved, and the independence among the Applets is enhanced so as to ensure that the access to an Applet data structure and the invoking of the interface methods from outside can be finished only through the threads of the Applets.

Description

technical field [0001] The invention relates to a calling method between computer componentized software, in particular to a calling method between components based on a thread model and the thread model. Background technique [0002] Each Applet component can be regarded as an independent application, a self-enclosed running space. Even if the Applets in the same process, the data between them is relatively independent, and each has its own thread to execute its own code. Clear Applet boundaries. [0003] However, when there is a call relationship between Applets, for example, an Applet in an address book may call an Applet in Email to complete the function of "clicking on an email address in the address book to directly pop up and edit a new email". There may be many calls between similar Applets. For an Applet, if its function implementation may be called concurrently by multiple Applets, or its code may run in different Applets, it may cause many unpredictable difficult...

AI Technical Summary

Problems solved by technology

[0003] However, when there is a call relationship between Applets, for example, an Applet in an address book may call an Applet in Email to complete the function of "clicking on an email address in the address book to directly pop up and edit a new email". There may be many calls between similar Applets. , for an Applet, if its function implementation may be called concurrently by multiple Applets, or its code may run in different Applets, it may cause many unpredictable difficulties and assumptions for Applet implementers

First of all, consider the mutual exclusion relationship of multi-threaded concurrent calls. For an Applet with simple functions, it may only need one Applet main thread to complete all functions, but in order to prevent it from being called by other Applets, multi-threading issues must be considered; For another example, all threads in the process belong to a certain Applet, then any Applet member method that calls Api to obtain the handle of the current Applet should be the Applet it belongs to, but since the Applet may be called by other Applets, the Applet handle it obtains Not sure which Applet it is, if its function implementation method depends on it, it will be more complicated to deal with

Therefore, when Applet calls each other, there is a problem of multi-threaded concurrent calls.

Images