CN108920150A - A kind of event management method and device - Google Patents
A kind of event management method and device Download PDFInfo
- Publication number
- CN108920150A CN108920150A CN201710234039.3A CN201710234039A CN108920150A CN 108920150 A CN108920150 A CN 108920150A CN 201710234039 A CN201710234039 A CN 201710234039A CN 108920150 A CN108920150 A CN 108920150A
- Authority
- CN
- China
- Prior art keywords
- event
- event data
- data object
- storage object
- storage
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/443—Optimisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3628—Software debugging of optimised code
Abstract
The present invention provides a kind of event management method and device, this method include：Step 1, when after event generation without carrying out response operation, in event storage object, the removal in event data object is corresponded to according to the event and monitors function, the target object of the event is removed and is monitored；Step 2, the event data object is removed from the event storage object.The present invention can be removed automatically all events by the event data object in traversal event storage object by being managed in event storage object to event.The event of addition is avoided because not removing in time, and wastes memory headroom, cause reference cannot be by garbage reclamation, while also avoiding constantly being added the memory overflow being likely to occur with event, and then ensure that the application program of exploitation works normally.
Description
Technical field
The present invention relates to computer application technologies, more particularly, to a kind of event management method and device.
Background technique
Event is identified can to operate, and such as presses confirming button, selects some radio button or check box.Using
When event-driven programming mode carries out application development, application developer would generally add many events.
If the event of addition does not use, remove not in time, memory headroom can be wasted, cause reference that cannot be returned by rubbish
It receives.And constantly added with event and result even in memory overflow, can not work normally the application program of exploitation.
In general, the event of these additions can not be recycled automatically, application developer is needed manually to remove.But due to these
The event of addition is scattered in code, cause manually to remove it is time-consuming and laborious when event, it is inconvenient.
Summary of the invention
The present invention provides a kind of event management method and device, to overcome in the prior art, the event of addition can not by from
Dynamic recycling.
According to an aspect of the present invention, a kind of event management method is provided, including：Step 1, it is not necessarily to after event generation
When carrying out response operation, in event storage object, the removal in event data object is corresponded to according to the event and monitors function,
The target object of the event is removed and is monitored；Step 2, the event data object is moved from the event storage object
It removes.
The possible implementation of with reference to first aspect the first, in the second possible implementation, step 1 it
Before further include：When needing to carry out response operation after event generation, based on the addition event functions in event memory interface,
The event is added and is stored in the event storage object.
The possible implementation of with reference to first aspect the first, in the third possible implementation, the step 1
Including：When operating without carrying out response after the generation of all events, in event storage object, each target object is traversed
Each corresponding event data object monitors function using the removal in the event data object, to the target object
It removes and monitors.
The possible implementation of with reference to first aspect the first, in the fourth possible implementation, the step 1
Including：When target object corresponds to after all events generate without carrying out response operation, in event storage object, it is based on event
Event data, obtain the corresponding target object of the event；Based on the target object, it is corresponding to obtain the target object
Event data object array；For each event data object in the event data object array, it is based on the event data
Function is monitored in the removal of object, is removed and is monitored to the target object.
The possible implementation of with reference to first aspect the first, in a fifth possible implementation, the step 1
Including：When after event generation without carrying out response operation, in event storage object, based on the event data of the event,
Using the acquisition event functions of the event storage object, the event data object of the event is obtained；Based on the event number
Function is monitored according to the removal of object, the target object of the event is removed and is monitored.
The possible implementation of second with reference to first aspect, it is in a sixth possible implementation, described to be based on
Addition event functions in event memory interface, are added the event and to be stored in the event storage object further
Including：Based on the event data of the event, event data object is created；The event data object of creation is stored to the thing
Part storage object.
The 6th kind of possible implementation with reference to first aspect, it is described to be based in the 7th kind of possible implementation
The event data of the event, creation event data object further comprise：Based on the event data of the event to be added, benefit
With the acquisition event functions in the event storage object, it is corresponding that the event to be added is obtained from the event storage object
Event data object；When not getting event data object, event data object is created.
The 7th kind of possible implementation with reference to first aspect, it is described to create in the 8th kind of possible implementation
The event data object built is stored to the event storage object：Using the target object of the event as described in
The key of event storage object obtains the corresponding value of the key from the event storage object；It, will based on the corresponding value of the key
The event data object of creation is stored to the event storage object.
The 8th kind of possible implementation with reference to first aspect, in the 9th kind of possible implementation, based on described
The corresponding value of key, the event data object of creation is stored to the event storage object includes：When the corresponding value of the key is
When empty, empty array object is created, the event data object of the creation is stored to the empty array object, the first array is obtained
Object；Using the target object parameter of the event to be added as key, using first array object as value, with key-value pair
Form is stored to the event storage object；When the corresponding value of the key is non-empty, by the event data object of the creation
It stores into the corresponding value of the key.
According to another aspect of the present invention, a kind of incident management device is provided, including：It removes and monitors module and removal mould
Block；Module is monitored in the removal, when for after event generating without carrying out response operation, in event storage object, according to
The event corresponds to the removal in event data object and monitors function, removes and monitors to the target object of the event；The shifting
Except module, for the event data object to be removed from the event storage object.
Event management method and device proposed by the present invention, when after event generation without carrying out response operation, in event
In storage object, the removal in event data object is corresponded to according to the event and monitors function, to the target object of the event
It removes and monitors；The event data object is removed from the event storage object.The present invention passes through in event storage object
In event is managed collectively, can by traversal event storage object in event data object, all events are automatic
It removes.Both make remove operation it is more succinct, in turn avoid addition event because not removing in time, and waste memory headroom,
Cause reference cannot be by garbage reclamation, while also avoiding constantly being added the memory overflow being likely to occur with event, into
And it ensure that the application program of exploitation and work normally.
Detailed description of the invention
Fig. 1 is a kind of event management method flow chart according to the embodiment of the present invention；
Fig. 2 is a kind of event management method flow chart according to the embodiment of the present invention；
Fig. 3 is a kind of event management method flow chart according to the embodiment of the present invention；
Fig. 4 is a kind of incident management schematic device according to the embodiment of the present invention.
Specific embodiment
With reference to the accompanying drawings and examples, specific embodiments of the present invention will be described in further detail.Implement below
Example is not intended to limit the scope of the invention for illustrating the present invention.
As shown in Figure 1, according to an aspect of the present invention, the embodiment of the present invention provides a kind of event management method, including：
Step 1, when after event generation without carrying out response operation, in event storage object, event number is corresponded to according to the event
Function is monitored according to the removal in object, the target object of the event is removed and is monitored；Step 2, by the event data object
It is removed from the event storage object.
In the present embodiment, event storage object is dictionary type, including key and value.Key is the target object of event；Value
For array, each array element is event data object.The corresponding event data object of one event.Event data object is used
In storage event data.Event data includes：Target object (Target), event type (Type), call back function
(Listener), whether bubbling (UseCapture) and priority (Priority).The function that event data object provides is at least
Function is monitored including removing.
Event management method proposed by the present invention, when after event generation without carrying out response operation, in event storage pair
As in, the removal in event data object is corresponded to according to the event and monitors function, prison is removed to the target object of the event
It listens；The event data object is removed from the event storage object.The present invention by event storage object to thing
Part is managed, and can be removed automatically all events by the event data object in traversal event storage object.Both made
Removal operation is more succinct, in turn avoids the event of addition because not removing in time, and wastes memory headroom, causes reference cannot
By garbage reclamation, while also avoiding constantly being added the memory overflow being likely to occur with event, and then ensure that exploitation
Application program work normally.
Based on the method that above-mentioned Fig. 1 corresponding embodiment provides, the embodiment of the invention provides a kind of event management method, ginsengs
See Fig. 2.This method includes：
101, when needing to carry out response operation after event generation, based on the addition event functions in event memory interface,
The event is added and is stored in the event storage object；
102, when operating without carrying out response after the generation of all events, in event storage object, traverse each
Each corresponding event data object of target object monitors function using the removal in the event data object, to described
Target object, which removes, to be monitored；
103, the event data object is removed from the event storage object.
Wherein, 101, when needing to carry out response operation after event generation, based on the addition event in event memory interface
Function is added the event and is stored in the event storage object.
Due to being managed by event storage object to event, it needs to add before being managed event
Event, and the event of addition is stored to event storage object.The present embodiment addition event and by the event of addition store to
When event storage object, the addition event functions of use are provided by event memory interface.The event storage that the present embodiment uses
The incident management function that device interface provides includes at least：It adds event functions and removes event functions.Event memory interface needs
It is created before addition event, creation code is as follows：
The incident management function type that the event memory interface provides can be extended according to actual treatment demand, with
Keep way to manage more diversified.
To event addition and storage mode, the present embodiment does not limit, including but not limited to：Thing based on event to be added
Number of packages evidence creates event data object；The event data object of creation is stored to the event storage object.
Further, for the event data based on event to be added, this reality of the concrete mode of event data object is created
Apply example also without limitation, including but not limited to：Based on the event data of the event to be added, the event storage object is utilized
In acquisition event functions, the corresponding event data object of the event to be added is obtained from the event storage object；When
When not getting event data object, event data object is created.
Specifically, by the event data of event to be added -- target object (Target), event type (Type), readjustment letter
Number (Listener), whether bubbling (UseCapture) and priority (Priority) -- as acquisition event functions incoming ginseng
Number, obtains the corresponding event data object of event to be added from event storage object.Before addition and storage event, it need to determine
Adopted event stores class, and creates event storage object.The function that event storage object provides includes at least：Obtain event functions.
When obtaining event functions return sky, illustrates event to be added and be not added with, therefore, event data object need to be created and added with treating
Event is added to be added.The creation of event data object includes storage being carried out to the event data of event to be added and to be added
The target object of event, which adds, to be monitored.The function that event data object provides includes at least：Function addEvent is monitored in addition
(), removeEvent (), which is removed, monitors function, compares function equip (), and first destroys function dispose ().Creation event
The specific code of data object is as follows：
After creating event data object, the event data object of creation need to be saved to the event storage object.It is right
It stores in by the event data object of creation to the concrete mode of the event storage object, the present embodiment also without limitation, wraps
It includes but is not limited to：Using the target object of the event to be added as the key of the event storage object, stored from the event
The corresponding value of the key is obtained in object；Based on the corresponding value of the key, the event data object of creation is stored to the thing
Part storage object.
When the corresponding value of the key is empty, create empty array object, by the event data object of the creation store to
The sky array object, obtains the first array object；Using the target object parameter of the event to be added as key, by described
One array object in the form of key-value pair, is stored to the event storage object as value；When the corresponding value of the key is non-empty
When, the event data object of the creation is stored into the corresponding value of the key.
Event data object is created, event to be added is added, and is stored specific to event storage object
Code is as follows：
Wherein, 102, after all events generate, when without carrying out response operation, in event storage object, traversal is every
Each corresponding event data object of one target object monitors function using the removal in the event data object, right
The target object, which removes, to be monitored.
Wherein, 103, the event data object is removed from the event storage object.
When needing to remove all events in event storage object, the event that can be used destroys the second pin that interface provides
Ruin function.Specifically, in event storage object, each corresponding event data object of each target object is traversed, benefit
Function is monitored with the removal in event data object, the target object that event data object corresponds to event is removed and is monitored, and will
All event data objects are removed from event storage object.Event destroys interface need to be busy to the institute in event storage object
Part creates before being destroyed.The event of creation destroys the function that interface provides and includes at least the second destruction function.
The creation code that event destroys interface is as follows：
It is as follows to adopt the code that the second destruction function removes all events in event storage object：
Based on the method that above-mentioned Fig. 1 corresponding embodiment provides, the embodiment of the invention provides a kind of event management method, ginsengs
See Fig. 3.This method includes：
201, when needing to carry out response operation after event generation, based on the addition event functions in event memory interface,
The event is added and is stored in the event storage object；
202, when after event generation without carrying out response operation, in event storage object, it is based on the event
Event data obtain the event data object of the event using the acquisition event functions of the event storage object；
203, function is monitored in the removal based on the event data object, is removed and is monitored to the target object of the event；
204, the event data object is removed from the event storage object.
Wherein, 201, when needing to carry out response operation after event generation, based on the addition event in event memory interface
Function is added the event and is stored in the event storage object.
Step 101 is identical in the detailed process of this step embodiment corresponding with Fig. 2, no longer repeats herein.
Wherein, 202, when after event generation without carrying out response operation, in event storage object, based on described
The event data of event obtains the event data object of the event using the acquisition event functions of the event storage object.
Specifically, it calls and obtains event functions, the process for obtaining the event data object of event includes：By the event of event
Incoming parameter of the data as acquisition event functions,
Using the target object of event as the key of event storage object, the corresponding event data object array of key is obtained, it is right
In each of array event data object, using the comparison function of the event data object, by the event data object
The event data of storage is compared with the event data of event, returns to the event data object when the two is identical, otherwise
It returns empty.The process specific code is as follows：
Wherein, 203, function is monitored in the removal based on the event data object, is removed to the target object of the event
It monitors.
Wherein, 204, the event data object is removed from the event storage object.
Event is removed, the removal event functions of event memory interface offer are provided.Specifically, by event
Target object obtains the corresponding event data object array of key as key, when array is empty, illustrates that event has been removed.When
When array is not sky, function is obtained by the event that event storage object provides, obtains the event data object of event.Utilize thing
The first destruction function that part data object provides, removes event.It specifically removes and includes：The removal of event data object is supervised
Function is listened, the target object of the event is removed and is monitored, sets empty for event data.It, will and when array length is 0
The array removes.The code of the process is as follows：
As shown in figure 4, according to another aspect of the present invention, the embodiment of the present invention provides a kind of incident management device, packet
It includes：It removes and monitors module, for for the event data object of event, utilizing the event data in event storage object
Function is monitored in removal in object, is removed and is monitored to the target object of the event；Wherein, the corresponding event number of an event
According to object；Remove module, for removing the event data object from the event storage object.
Incident management device proposed by the present invention monitors module by removing, without carrying out response behaviour after event generates
When making, in event storage object, the removal in event data object is corresponded to according to the event and monitors function, to the event
Target object remove monitor, by remove module, the event data object is removed from the event storage object.This
Invention can pass through the event data pair in traversal event storage object by being managed in event storage object to event
As all events are removed automatically.Both make removal operation more succinct, in turn avoid the event of addition because of no and time shift
It removes, and wastes memory headroom, causes reference cannot be by garbage reclamation, while also avoiding constantly being added possibility with event
The memory overflow of appearance, and then ensure that the application program of exploitation works normally.
As a kind of alternative embodiment, described device further includes：Memory module is added, for needing after event generation
When carrying out response operation, based on the addition event functions in event memory interface, the event is added and is stored in institute
State event storage object.
As a kind of alternative embodiment, module is monitored in the removal, be specifically used for being not necessarily to after all events generate into
When row response operation, in event storage object, each corresponding event data object of each target object is traversed, is utilized
Function is monitored in removal in the event data object, is removed and is monitored to the target object.
As a kind of alternative embodiment, module is monitored in the removal, is specifically used for producing when target object corresponds to all events
When after life without carrying out response operation, in event storage object, based on the event data of the event, the event pair is obtained
The target object answered；Based on the target object, the corresponding event data object array of the target object is obtained；For described
Each event data object in event data object array, function is monitored in the removal based on the event data object, to described
Target object, which removes, to be monitored.
As a kind of alternative embodiment, module is monitored in the removal, specifically for being not necessarily to be responded after event generates
When operation, in event storage object, based on the event data of the event, the acquisition event of the event storage object is utilized
Function obtains the event data object of the event；Function is monitored in removal based on the event data object, to the event
Target object remove monitor.
As a kind of alternative embodiment, the addition memory module includes creating unit and storage unit；The creation is single
Member creates event data object for the event data based on the event；The storage unit, the event for will create
Data object is stored to the event storage object.
As a kind of alternative embodiment, the creating unit, specifically for the event data based on the event to be added,
Using the acquisition event functions in the event storage object, the event pair to be added is obtained from the event storage object
The event data object answered；When not getting event data object, event data object is created.
As a kind of alternative embodiment, the storage unit, specifically for using the target object of the event as described in
The key of event storage object obtains the corresponding value of the key from the event storage object；It, will based on the corresponding value of the key
The event data object of creation is stored to the event storage object.
As a kind of alternative embodiment, the storage unit is further specifically used for when the corresponding value of the key is empty,
Empty array object is created, the event data object of the creation is stored to the empty array object, the first array object is obtained
Using the target object parameter of the event to be added as key, using first array object as value, in the form of key-value pair,
It stores to the event storage object；When the corresponding value of the key is non-empty, the event data object of the creation is stored
To in the corresponding value of the key.
Finally, method of the invention is only preferable embodiment, it is not intended to limit the scope of the present invention.It is all
Within the spirit and principles in the present invention, any modification, equivalent replacement, improvement and so on should be included in protection of the invention
Within the scope of.
Claims (10)
1. a kind of event management method, which is characterized in that including：
Step 1, when after event generation without carrying out response operation, in event storage object, thing is corresponded to according to the event
Function is monitored in removal in part data object, is removed and is monitored to the target object of the event；
Step 2, the event data object is removed from the event storage object.
2. the method according to claim 1, wherein further including before step 1：It is needed after event generation
When carrying out response operation, based on the addition event functions in event memory interface, the event is added and is stored in institute
State event storage object.
3. the method according to claim 1, wherein the step 1 includes：
When operating without carrying out response after the generation of all events, in event storage object, each target object is traversed
Each corresponding event data object monitors function using the removal in the event data object, to the target object
It removes and monitors.
4. the method according to claim 1, wherein the step 1 includes：
When target object corresponds to after all events generate without carrying out response operation, in event storage object, based on described
The event data of event obtains the corresponding target object of the event；
Based on the target object, the corresponding event data object array of the target object is obtained；
For each event data object in the event data object array, the removal based on the event data object is monitored
Function removes the target object and monitors.
5. the method according to claim 1, wherein the step 1 includes：
When after event generation without carrying out response operation, in event storage object, based on the event data of the event, benefit
With the acquisition event functions of the event storage object, the event data object of the event is obtained；
Function is monitored in removal based on the event data object, is removed and is monitored to the target object of the event.
6. according to the method described in claim 2, it is characterized in that, the addition event letter based in event memory interface
Number, is added the event and is stored in the event storage object and further comprise：
Based on the event data of the event, event data object is created；
The event data object of creation is stored to the event storage object.
7. according to the method described in claim 6, it is characterized in that, the event data based on the event, creates event
Data object further comprises：
It is deposited using the acquisition event functions in the event storage object from the event based on the event data of the event
The corresponding event data object of the event is obtained in storage object；
When not getting event data object, event data object is created.
8. the method according to the description of claim 7 is characterized in that described store the event data object of creation to the thing
Part storage object further comprises：
Using the target object of the event as the key of the event storage object, from the event storage object described in acquisition
The corresponding value of key；
Based on the corresponding value of the key, the event data object of creation is stored to the event storage object.
9. according to the method described in claim 8, it is characterized in that, the corresponding value of the key is based on, by the event data of creation
Object is stored to the event storage object：
When the corresponding value of the key is empty, empty array object is created, the event data object of the creation is stored to described
Empty array object obtains the first array object；Using the target object parameter of the event to be added as key, by first number
Group objects in the form of key-value pair, is stored to the event storage object as value；
When the corresponding value of the key is non-empty, the event data object of the creation is stored into the corresponding value of the key.
10. a kind of incident management device, which is characterized in that including：It removes and monitors module and remove module；
Module is monitored in the removal, when for after event generating without carrying out response operation, in event storage object, according to
The event corresponds to the removal in event data object and monitors function, removes and monitors to the target object of the event；
The remove module, for removing the event data object from the event storage object.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710234039.3A CN108920150A (en) | 2017-04-11 | 2017-04-11 | A kind of event management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710234039.3A CN108920150A (en) | 2017-04-11 | 2017-04-11 | A kind of event management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108920150A true CN108920150A (en) | 2018-11-30 |
Family
ID=64402594
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710234039.3A Pending CN108920150A (en) | 2017-04-11 | 2017-04-11 | A kind of event management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108920150A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111813695A (en) * | 2020-08-21 | 2020-10-23 | 网易（杭州）网络有限公司 | Code detection method, device, medium and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20010054061A1 (en) * | 2000-06-03 | 2001-12-20 | Noritaka Koyama | Object supplying device |
| CN103885757A (en) * | 2012-12-20 | 2014-06-25 | 上海明想电子科技有限公司 | Javascript event monitoring management method |
| CN104503748A (en) * | 2014-12-12 | 2015-04-08 | 珠海金山网络游戏科技有限公司 | Editor system and method based on event driving |
| CN105094811A (en) * | 2015-06-29 | 2015-11-25 | 安一恒通（北京）科技有限公司 | Method can device for processing events |
| CN106339217A (en) * | 2016-08-18 | 2017-01-18 | 福建天泉教育科技有限公司 | Event management method and system based on Unity |
-
2017
- 2017-04-11 CN CN201710234039.3A patent/CN108920150A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20010054061A1 (en) * | 2000-06-03 | 2001-12-20 | Noritaka Koyama | Object supplying device |
| CN103885757A (en) * | 2012-12-20 | 2014-06-25 | 上海明想电子科技有限公司 | Javascript event monitoring management method |
| CN104503748A (en) * | 2014-12-12 | 2015-04-08 | 珠海金山网络游戏科技有限公司 | Editor system and method based on event driving |
| CN105094811A (en) * | 2015-06-29 | 2015-11-25 | 安一恒通（北京）科技有限公司 | Method can device for processing events |
| CN106339217A (en) * | 2016-08-18 | 2017-01-18 | 福建天泉教育科技有限公司 | Event management method and system based on Unity |
Non-Patent Citations (2)
| Title |
|---|
| DEAN EDWARDS: "addEvent() – My Solution", 《HTTP://DEAN.EDWARDS.NAME/WEBLOG/2005/10/ADD-EVENT/》 * |
| 唐国纯: "《Flash CS5精品动画设计与制作》", 30 June 2012 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111813695A (en) * | 2020-08-21 | 2020-10-23 | 网易（杭州）网络有限公司 | Code detection method, device, medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110597616B (en) | Memory allocation method and device for neural network | |
| CN103514102B (en) | A kind of Java Virtual Machine realizes the method and device of internal memory garbage reclamation | |
| CN100386745C (en) | Method and apparatus for dynamic memory management within an object-oriented program | |
| CN1735043A (en) | Method, system, and cluster for the update of management objects | |
| CN1866283B (en) | System and method for implementing regular system triggering | |
| CN1755720A (en) | Methods and systems for caching and synchronizing project data | |
| CN106302632A (en) | The method for down loading of a kind of foundation image and management node | |
| CN1855057A (en) | System and method for providing bundle group termination in an OSGi service platform | |
| CN112269640A (en) | Method for realizing life cycle management of container cloud component | |
| Kim et al. | SELCOM: Selective compression scheme for lightweight nodes in blockchain system | |
| CN108509284A (en) | A kind of tree shaped model task management system applied to functional expression programming | |
| CN108920150A (en) | A kind of event management method and device | |
| CN101303762A (en) | Method for managing primitive of automatization system based on dynamically loading and plug-in unit technique | |
| CN103593300A (en) | Memory allocating and collecting method | |
| CN100357889C (en) | Method for managing long-distance structural components service cycle with class as unit | |
| CN101694661B (en) | Method and device for generating statistical form and statistical server | |
| CN110493571B (en) | Cross-regional cluster cascading service data distribution method, device and monitoring system | |
| CN103019819A (en) | Dynamic link library uniform scheduling method based on plug-in mechanism | |
| CN108228342A (en) | Terminal equipment control method and device, terminal device and computer readable storage medium | |
| CN102196392A (en) | Method and equipment for sending signaling tracing message | |
| CN108268605A (en) | A kind of communal space method for managing resource and system | |
| CN111897643A (en) | Thread pool configuration system, method, device and storage medium | |
| CN110018866B (en) | User interface theme updating method, device and system, vehicle machine and vehicle | |
| CN105760424A (en) | Database establishment method for storing key data of enterprise products | |
| Hsieh | Reconfigurable fault tolerant deadlock avoidance controller synthesis for assembly production processes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20181130 |