Free Computer Repair Service

The existing cross-component messaging technology is based on the principles of the sender information Components and the receiver must use the messaging service interface to send and receive messages. Phase Related industry standards including JMS and CORBA event service, etc., the corresponding products Has been to maturity, such as IBM’s MQSeries and WBI ⋯.

 In addition, the Asynchronous Event Service. The rationale for the framework DAEHF), they all make use of asynchronous messages and loosely coupled to Force, as a heterogeneous system integration solutions. Can be message-oriented Middleware as the events surrounding the mechanisms of the further strengthening and expansion of Qualcomm Providing security, services and durable service provider makes the news and information consumption Between the more loosely coupled and reliable. However, these elements of existing technology and interactive Products, including theoretical studies [3 to 51 including a common feature of them is based on the pre – First message service interface defined by the message sender / receiver to use the access I: I significantly Type to send / receive messages.

 Its disadvantages is that an explicit call to increase the existence of code Additional workload and error probability, but also because it is usually by modifying / Generated source code to achieve the one hand it is difficult to achieve binary compatibility, in order to facilitate both Keep reusable binary components, and secondly because the relevant source code to be forced to join the Events / news to support the code, do not only need the events / messages in support of the components Examples of the introduction of event-based / interactive components to support information.

 They lack will Events / news seamlessly interactive mechanism, transparent integration with the practical application of the specific side Law, and further lead to the problem is that the use of the complex is not conducive to the introduction of a Suitable for applications of all sizes in a simple, unified model.

 The events/information mechanism has the following characteristics:

(1) The concept of events to introduce an automatic and transparent, seamless support for the introduction of the incident Mechanism. Event-triggered components at the time of loading code / run-time components to be inserted into the Second Hexadecimal code execution, in the component method calls automatically trigger events, and, Through the use of XML configuration, such as events, makes the definition independent of the source of the incident on behalf of

Code and binary code, no longer require developers to explicitly call a specific message / Event Service API, eliminating the need for a specific event service API dependency.

(2) Event run-time support system using a simple, unified incident mode Type, a consistent approach to dealing with all types of events. Whether it is automatic incident Or explicitly call the event service API events generated (hereinafter referred to as manual thing Cases), or a reflection of events of the router to generate a state of the incident the way routers work By the events, run-time support system is not indiscriminate, consistent handling, coupled with the node All use of the container components, run-time support system can be seamlessly embedded in should be Use system.

(3) Support system run-time events to provide nested to support the state has a flexible routing mechanism for routing services events. Events triggered from the router component is responsible for connecting components and the receiver, in between the components Transfer case; router itself is the component at the same time, the issue of routing events and their incident as an example, he can be non-router receiving component (which may further trigger a new Events), can also be received and forwarded to other routers in order to form a thing Pieces of the router network components connected to the network routing the event, by sending and Receive interactive events, but the component itself has no need to keep aware of the routing network In or not, the routing network is responsible for scheduling the trigger component in the incident and receiving inter-component mass Delivery of events, become the core of the interactive components, the introduction of automatic incident highlights the extinction The difference between income and Events: “news” is explicit rather than take the initiative to send a passive trigger.