CN105677536A - Implementing method for task messages and task system for implementing task messages - Google Patents
Implementing method for task messages and task system for implementing task messages Download PDFInfo
- Publication number
- CN105677536A CN105677536A CN201610010842.4A CN201610010842A CN105677536A CN 105677536 A CN105677536 A CN 105677536A CN 201610010842 A CN201610010842 A CN 201610010842A CN 105677536 A CN105677536 A CN 105677536A
- Authority
- CN
- China
- Prior art keywords
- task
- message
- task message
- new channel
- module
- 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
Abstract
The invention provides an implementing method for task messages and a task system for implementing task messages. The implementing method for the task messages comprises the following steps of S10, establishing a new channel; S20, the task messages are established in the new channel; S30, monitoring all the task messages in the new channel; S40, screening out the task message triggered in the new channel according to preset keywords; S50, analyzing a first parameter field in the screened triggered task message, and executing a task event contained in the task message. Compared with existing task messages such as a timed task implementing method, source codes do not need to be modified greatly, and the purpose of rapidly and efficiently sending the task only by adding the monitoring the new channel in a database is achieved.
Description
Technical field
The present invention relates to communication technical field, particularly relate to a kind of method that realizes of task message and realize the task system of this task message.
Background technology
In order to pursue more efficient work efficiency, it is required at present setting task message in a lot of operation systems, below for timed task: as, extension system is expected to certain time point and goes to switch the advertisement thrown on certain advertising platform, to increase the exposure rate of different advertisement, it is accomplished by arranging timed task in extension system, when timed task expires, extension system switching advertising platform needs the advertisement being launched; And for example, a user recommends another user and registers some websites, it is possible to set a timed task, and the recommended user that looks at that time is up is either with or without registration, if no registration does not just push a note to him and goes over; For another example, when morning every day, in software system, the log information etc. of the previous day of timing analysis is required for timed task. It can be seen that timed task is possible not only to improve work efficiency can be substantially reduced human cost simultaneously.
The method that realizes of present timed task has a lot, e.g., generally adopts crontab technology to perform timed task under Linux environment, and it reads instruction from standard input device, and deposited with in " crontab " file, for reading afterwards and execution; And for example, java field adopts Springquartz technical finesse timed task, and is timed the configuration etc. of task by configuration file.
But, the realization of existing task message all binds together with other service logics and task is divided into multiple subtask and realizes, as, when timed task revised by needs, stop firstly the need of by software service, its source code is modified, more amended software system is redeployed to server subsequently. Improve risk and the difficulty of system maintenance so undoubtedly, and implement relatively complicated.
Summary of the invention
For the problems referred to above, the invention provides a kind of method that realizes of task message and realize the task system of this task message, it realizes monitoring and the process of timed task by monitoring client, complete and original system decoupling, it is easy to maintenance and expansion.
Technical scheme provided by the invention is as follows:
A kind of method that realization of task message, the method that realizes of described task message comprises the following steps:
S10 creates new channel;
S20 creates task message in described new channel;
S30 monitors all of task message in described new channel;
S40 screens the task message being triggered in described new channel according to preset keyword;
S50 resolves the first parameter field in the task message being triggered that screening obtains, and performs the task events comprised in described task message.
It is further preferred that in step slo, specifically include:
Obtain the title of new channel, and the title of described new channel is compared with existing channel designation; If finding, it conflicts with existing channel designation, then report to the police; If not conflicting with existing channel designation, then in data base, create new channel with this title.
It is further preferred that in step S20, specifically include:
New channel described in S21 receives task message;
Described task message is compressed into key by S22, and sets the key name that described task message is corresponding;
S23 triggers the second parameter field of described task message according to the type set of described task message;
S24 stores key name corresponding to described task message, described task message and triggers the second parameter field of described task message.
It is further preferred that specifically include in step s 30:
S31 subscribes to described new channel;
Whether S32 monitors in described new channel has task message to be triggered, if not having, then continues to monitor; If having, jump to step S40;
Specifically include in step s 40:
S41 receives associating with described task message of the task triggering message that described data base pushes, and triggers the task message of message relating according to preset keyword screening and described task.
It is further preferred that in step S20, specifically include:
New channel described in S211 receives timed task;
Described timed task is compressed into key by S221, and sets the key name that described timed task is corresponding;
The expired time of described timed task is set as triggering the second parameter field of described timed task by S231;
S241 stores key name corresponding to described timed task, described timed task and described expired time.
It is further preferred that specifically include in step s 30:
S311 subscribes to described new channel;
S321 monitors whether the expired time of timed task in described new channel expires, if not having, then continues to monitor; If having, push the outdated information associated with described timed task;
Specifically include in step s 40:
S42 receives described outdated information, and screens the task message associated with described outdated information according to preset keyword;
Specifically include in step s 50:
Resolve the first parameter field in the timed task being triggered that screening obtains, perform the expired events comprised in described task message.
It is further preferred that in step s 40, described preset keyword is particularly as follows: the type of task message and/or key name and the/the first parameter field;
In step s 50, described first parameter field is specially the parameter field identifying described task events.
Present invention also offers a kind of task system for realizing task message, described task system includes: data base, monitoring client and business end, wherein, described data base is connected with described monitoring client and described business end respectively, and described business end release tasks message is to the new channel of described data base; Described data base receives described task message and stores; Whether described monitoring client monitor in real time storage task message in the database is triggered, and then judges whether to perform task events.
It is further preferred that include in the database:
Setting module, for creating new channel in the database, and for setting key name corresponding to the task message received and the second parameter field of the type set described task message of triggering according to described task message;
First information receiver module, is connected with described business end, for receiving the described task message that described business end sends;
Compression module, is connected with described information receiving module, and the described task message received is compressed into the key of correspondence;
Memory module, is connected with described setting module, described information receiving module and described compression module respectively, and described memory module is for storing key name corresponding to described task message, described task message and triggering the second parameter field of described task message;
First information sending module, is connected with described monitoring client and described memory module respectively, is used for the task that sends and triggers message extremely described monitoring client;
Described monitoring client includes:
Second information receiving module, is used for receiving described task and triggers message;
Screening module, is connected with described second information receiving module, and described screening module for triggering the task message of message relating according to preset keyword screening and described task;
Parsing module, is connected with described screening module, and described parsing module resolves the first parameter field in the task message that screening obtains;
Task execution module, with described parsing module, described task execution module performs the task events wherein comprised according to the analysis result of described parsing module.
The method that realizes of task message provided by the invention and realize the task system of this task message, it is possible to bring following beneficial effect:
In the present invention, by adding new channel in data base, then all information in this new channel are monitored, once we want a certain task message of monitoring to be triggered in this new channel, then this monitoring client performs just to trigger message according to sending in data base of task and performs the task events in this task message, finds corresponding user to send corresponding message etc. Relative to existing task message, method is realized such as timed task, source code need not be revised by method provided by the invention in a large number, only need to add a new channel the purpose being monitored just rapidly and efficiently realizing transmission task to it in data base. Instant user is not online, it is also possible to this off-line PUSH message is retained, and treats that user reaches the standard grade and retransmits away.
Further, in the present invention, if needing add in task system or revise a certain task message, as revised a certain timed task, it is only necessary to revise corresponding tasks carrying function just; And we use node.js as monitoring client, the new channel in data base to be monitored in a specific embodiment so that it is full decoupled with business end, whole system is easily maintained and extends.
Accompanying drawing explanation
Below by the way of clearly understandable, accompanying drawings preferred implementation, above-mentioned characteristic, technical characteristic, advantage and implementation thereof are further described.
Fig. 1 be task message provided by the invention realize method flow schematic diagram;
Fig. 2 is the structural representation of task system provided by the invention;
Fig. 3 is the structural representation of data base provided by the invention;
Fig. 4 is the structural representation of monitoring client provided by the invention.
Drawing reference numeral illustrates:
100-task system, 110-data base, 120-monitoring client, 130-business end, 121-setting module, 122-first information receiver module, 123-compression module, 124-memory module, 125-first information sending module, 131-the second information receiving module, 132-screens module, 133-parsing module, 134-task execution module.
Detailed description of the invention
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, below comparison accompanying drawing is illustrated the specific embodiment of the present invention. Apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the premise not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings, and obtain other embodiment.
It is known that Node.js is a platform set up when running based on ChromeJavaScript, for building fast response time easily, being prone to the network application of extension. Node.js uses event-driven, Non-Blocking I/O model and be able to light weight and efficiently, the data-intensive real-time application being highly suitable on distributed apparatus to run. Redis is that a key-value stores system. Redis supports master-slave synchronisation. Data can synchronize from master server to any number of from server, can be associate other master servers from server from server. This makes Redis can perform monolayer tree copying. Data consciously or unconsciously can be carried out write operation by deposit. Owing to fully achieving publish/subscribe mechanism so that during from data base's synchronization tree anywhere, a channel can be subscribed to and receive the news release record that master server is complete.
Publish/subscribe (pub/sub) is a kind of messaging mode, and main purpose is the coupling between decoupling message issuer and message subscribing person. Pub/sub not only solves publisher and the coupling of subscriber's direct code rank, also solves both couplings on physics is disposed. Redis, as a pub/subserver (server), serves the function of message route between subscriber and publisher. Subscriber can pass through subscribe and psubscribe order and subscribe to oneself type of message interested to redisserver, and type of message is called channel (channel) by redis. When publisher sends certain types of message by publish order to redisserver, the whole users subscribing to this type of message can receive this message. Here the transmission of message is multi-to-multi. One user can subscribe to multiple channel, and system can also send message to multiple channels simultaneously.
By above description it is understood that, Node.js uses event-driven, and in redis data base, have some events, such as, key (key) expires, key is deleted, these events we just can realize by configuring redis data base, make once trigger these events just toward specific channel propelling movement a piece of news in redis data base, now, as long as we monitor this specific channel, can be achieved with purpose, perform task events therein. Thus, we provide a kind of method that realizes of task message and realize the task system of this task message, it uses pub/sub instruction to realize in node.js or browser by javascript, be illustrated in figure 1 in the present invention provide task message realize method flow schematic diagram, it can be seen that realize method specifically includes following steps in this task message: S10 creates new channel; S20 creates task message in new channel; S30 monitors all of task message in new channel; S40 screens the task message being triggered in new channel according to preset keyword; S50 resolves the first parameter field in the task message being triggered that screening obtains, and performs the task events comprised in task message.
In this embodiment, create in the process of new channel in step S10, specifically include following steps: obtain the title of new channel, and the title of described new channel is compared with existing channel designation; If finding, it conflicts with existing channel designation, then report to the police; If not conflicting with existing channel designation, then in data base, create new channel with this title. The title of the new channel namely created to be different from the title of existing database mid band, in order to avoid obscuring occurs in follow-up monitoring. As in a specific embodiment, above-mentioned data base is redis data base, we are intended to set up new channel in this redis data base, and the title of this new channel is set to " foo ", then in the process created, if having had channel in existing database is this title, then can not again with this new channel of this name creation.
Further, in another embodiment, create in the process of new channel in step S10, specifically include following steps: S11 creates new memory area in data base; S12 obtains the title of new channel, and the title of new channel is compared with existing channel designation; If finding, it conflicts with existing channel designation, then report to the police; If not conflicting with existing channel designation, then in new memory area, create new channel with this title. By above-mentioned it is understood that, here data base is specially redis data base, redis data base create in the process of new channel, in order to not allow follow-up monitoring occur obscuring, we open up a new memory area specially in data base, as, db is set to 1 in redis database manipulation, and (db value is defaulted as 0, db0 would be likely to occur originally and need the task message type of monitoring), so, we are it is ensured that the task message that we monitor is all the task message needing monitoring. In a specific embodiment, such as, it would be desirable to monitoring is all of expired events in certain db, if then before we monitor this db, there is expired events in the inside, then is not that the expired events that our task triggers also can send, occurs that key name resolves the situation of mistake.
In this embodiment, in step S20, specifically include: S21 new channel receives task message; Task message is compressed into key by S22, and sets the key name that task message is corresponding; S23 triggers the second parameter field of task message according to the type set of task message; Key name that S24 store tasks message, task message are corresponding and trigger the second parameter field of task message. Specifically, in an embodiment, after having established new channel in redis data base, service server or user just can to release tasks message in this new channel. After Redis data base have received task message, this task message will be compressed into a key, and set corresponding key name, set the second parameter field afterwards, finally corresponding content is stored. After this, when some key stored in redis data base is once be triggered, then redis data base will push out corresponding task triggering message, now, monitoring client (node.js) carries out corresponding task events (performing corresponding mission function) after have received this task triggering message. Specifically, in actual applications, the second parameter field here, can be set according to the type of specific tasks message, as when the task message received is timed task, then this second parameter field can be the expired time etc. of this timed task, and this is not construed as limiting by we. Additionally, it is noted that the title that only can pass key due to the event in redis data base, key assignments can't be transmitted, and in some cases, when triggering such as expired events, that key of triggering without, nature cannot obtain the key assignments of this key, therefore, as a rule, we are when the name of setting key, all information are put in the title of this key. As, in a specific embodiment, the type of task message is put in this title, even the path of this task message is put in this title, it is possible to be set according to practical situation.
After each data have all been stored by Redis data base, it is possible to start this new channel is monitored, specifically, in step s 30, including: S31 subscribes to new channel; Whether S32 monitors in new channel has task message to be triggered, if not having, then continues to monitor; If having, jump to step S40. Specifically include in step s 40: receive associating with task message of the task triggering message that data base pushes, and trigger the task message of message relating according to preset keyword screening and task. More particularly, preset keyword here includes: the type of task message and/or key name and the/the first parameter field. In a specific embodiment, if this preset keyword is the type of task message, and the type of this task message is specially expired events, then monitoring client 120 is after receiving task and triggering message, it will be screened, see that receiving of task triggers whether message is expired events, if not, then it is not carried out corresponding task events, if, then enter subsequent step S50, resolve the first parameter field in the task message being triggered that screening obtains, perform the task events comprised in task message.
As a complete embodiment, we for above-mentioned task events be expired events, task message for timed task, above procedure is described in detail:
In redis data base: the timed task that S211 new channel reception service server or user send over; Timed task is compressed into key by S221redis data base, and sets the key name that timed task is corresponding; The expired time of timed task is set as triggering the second parameter field of timed task by S231, and namely this expired time is the time difference performed from this timed task; S241 stores key name corresponding to timed task, timed task and expired time. Afterwards, once key expires (expired time expires), then just illustrating to have arrived the time performing this timed task, redis data base just pushes out outdated information.
In node.js monitoring client: S311 subscribes to this new channel; S321 monitors whether the expired time of timed task in this new channel expires, if not having, then continues to monitor; If having, redis data base pushes the outdated information associated with timed task; S42node.js monitoring client receives the outdated information that redis data base pushes, and screens the task message associated with outdated information according to preset keyword; S51 resolves the first parameter field in the timed task being triggered that screening obtains, and performs the expired events comprised in task message. Specifically, the first parameter field in step S50 and step S51 is specially the parameter field of mark task events, as in a specific embodiment, this first parameter field is for sending reminding short message, then node.js monitoring client is after being resolved to this first parameter field, sends reminding short message to corresponding user immediately. In other embodiments, the first parameter field here is set according to specific tasks.
More particularly, in node.js monitoring client, when we receive a timed task, then we can obtain the message content of this timed task, function name, expired time etc., is similar to: varsampleTaskMaker=function (message, func, timeout) { }, wherein message is message content, and func is function name, and timeout is expired time. So, when our node.js monitoring client is subscribed to after successfully this new channel concurrently set monitoring and tasks carrying function sampleOnExpired, as long as it is just passable when generating timed task, relevant parameter to be passed to sampleTaskMaker. Timed task in Redis data base is automatically expired and the event that triggers is to sampleOnExpired function, then node.js monitoring client will go to perform corresponding timed task and process function. Send out reminding short message such as to user's timing, then, it is only necessary to add the execution function sending reminding short message at this just passable. And if needs are revised or add timed task, also have only to add or revise this tasks carrying function, and the parameter of response is passed to sampleTaskMaker.
In another embodiment, further comprising the steps of in step s 30: to generate configuration file, configuration database according to the type of task message and/or the first parameter field.
It is illustrated in figure 2 the structural representation of the task system 100 for realizing task message provided by the invention, task system 100 includes: data base 110, monitoring client 120 and business end 130, wherein, data base 110 is connected with monitoring client 120 and business end 130 respectively, and business end 130 release tasks message is to the new channel of data base 110; Data base 110 receives task message and stores; Monitoring client 120 monitor in real time is stored in whether the task message in data base 110 is triggered, and then judges whether to perform task events. In a particular embodiment, data base 110 here is redis data base, and monitoring client 120 is node.js monitoring client, and business end 130 is service server or user.
Furthermore, include data base 110: setting module 121, for creating new channel in data base 110, and for setting key name corresponding to the task message received and the second parameter field of the type set triggering task message according to task message; First information receiver module 122, is connected with business end 130, for receiving the task message that business end 130 sends; Compression module 123, is connected with information receiving module, and the task message received is compressed into the key of correspondence; Memory module 124, is connected with setting module 121, information receiving module and compression module 123 respectively, and memory module 124 is for key name corresponding to store tasks message, task message and the second parameter field triggering task message; First information sending module 125, is connected with monitoring client 120 and memory module 124 respectively, is used for sending task and triggers message to monitoring client 120.
In the course of the work, first we create new channel first by setting module 121 in data base 110; Subsequently, first information receiver module 122 receives the task message that business end 130 sends; Receiving, this task message is compressed into key by compression module 123, and uses setting module 121 to set key name corresponding to this task message the second parameter field according to the type set triggering task message of task message; Then memory module 124 store tasks message, task message are corresponding key name and trigger the second parameter field of task message. Afterwards, in this redis data base 110, when task message is triggered, then by first information sending module 125, this task is triggered message immediately and send to monitoring client 120. Specifically, the second parameter field here, it is set according to the type of specific tasks message, if task message is timed task, then this second parameter field is the expired time etc. of this timed task, and this is not construed as limiting by we.
Monitoring client 120 includes: the second information receiving module 131, is used for the task that receives and triggers message; Screening module 132, is connected with the second information receiving module 131, and screening module 132 for triggering the task message of message relating according to preset keyword screening and task; Parsing module 133, is connected with screening module 132, and parsing module 133 resolves the first parameter field in the task message that screening obtains; Task execution module 134, with parsing module 133, task execution module 134 performs the task events wherein comprised according to the analysis result of parsing module 133. In the course of the work, first the second information receiving module 131 receives the task triggering message that number data base 110 sends, then screening module 132 for triggering the task message of message relating according to preset keyword screening and task, parsing module 133 resolves the first parameter field in the task message that screening obtains afterwards, and last task execution module 134 performs the task events wherein comprised according to the analysis result of parsing module 133.
Specifically, above-mentioned preset keyword includes: the type of task message and/or key name and the/the first parameter field. In a specific embodiment, if this preset keyword is the type of task message, and the type of this task message is specially expired events, then monitoring client 120 is after receiving task and triggering message, it will be screened, see that receiving of task triggers whether message is expired events, if it is not, be then not carried out corresponding task events. First parameter field is specially the parameter field of mark task events, as in a specific embodiment, this first parameter field is for sending reminding short message, then monitoring client is after being resolved to this first parameter field, sends reminding short message to corresponding user immediately.
As seen from the above description, provided by the invention realize method and task system, relative to existing task message, method is realized such as timed task, source code need not be revised by a large number, only need to add a new channel the purpose being monitored just rapidly and efficiently realizing transmission task to it in data base. And use node.js as monitoring client, the new channel in data base to be monitored so that it is full decoupled with business end, whole system is easily maintained and extends.
It should be noted that, above-described embodiment all can independent assortment as required. The above is only the preferred embodiment of the present invention; it should be pointed out that, for those skilled in the art, under the premise without departing from the principles of the invention; can also making some improvements and modifications, these improvements and modifications also should be regarded as protection scope of the present invention.
Claims (10)
1. a task message realize method, it is characterised in that the method that realizes of described task message comprises the following steps:
S10 creates new channel;
S20 creates task message in described new channel;
S30 monitors all of task message in described new channel;
S40 screens the task message being triggered in described new channel according to preset keyword;
S50 resolves the first parameter field in the task message being triggered that screening obtains, and performs the task events comprised in described task message.
2. task message as claimed in claim 1 realize method, it is characterised in that in step slo, specifically include:
Obtain the title of new channel, and the title of described new channel is compared with existing channel designation; If finding, it conflicts with existing channel designation, then report to the police; If not conflicting with existing channel designation, then in data base, create new channel with this title.
3. task message as claimed in claim 2 realize method, it is characterised in that in step S20, specifically include:
New channel described in S21 receives task message;
Described task message is compressed into key by S22, and sets the key name that described task message is corresponding;
S23 triggers the second parameter field of described task message according to the type set of described task message;
S24 stores key name corresponding to described task message, described task message and triggers the second parameter field of described task message.
4. task message as claimed in claim 3 realize method, it is characterised in that
Specifically include in step s 30:
S31 subscribes to described new channel;
Whether S32 monitors in described new channel has task message to be triggered, if not having, then continues to monitor; If having, jump to step S40;
Specifically include in step s 40:
S41 receives associating with described task message of the task triggering message that described data base pushes, and triggers the task message of message relating according to preset keyword screening and described task.
5. task message as claimed in claim 3 realize method, it is characterised in that in step S20, specifically include:
New channel described in S211 receives timed task;
Described timed task is compressed into key by S221, and sets the key name that described timed task is corresponding;
The expired time of described timed task is set as triggering the second parameter field of described timed task by S231;
S241 stores key name corresponding to described timed task, described timed task and described expired time.
6. task message as claimed in claim 5 realize method, it is characterised in that
Specifically include in step s 30:
S311 subscribes to described new channel;
S321 monitors whether the expired time of timed task in described new channel expires, if not having, then continues to monitor; If having, push the outdated information associated with described timed task;
Specifically include in step s 40:
S42 receives described outdated information, and screens the task message associated with described outdated information according to preset keyword;
Specifically include in step s 50:
Resolve the first parameter field in the timed task being triggered that screening obtains, perform the expired events comprised in described task message.
7. the task message as described in claim 4 or 6 realize method, it is characterised in that
In step s 40, described preset keyword is particularly as follows: the type of task message and/or key name and the/the first parameter field;
In step s 50, described first parameter field is specially the parameter field identifying described task events.
8. the task system being used for realizing task message, it is characterized in that, described task system includes: data base, monitoring client and business end, wherein, described data base is connected with described monitoring client and described business end respectively, and described business end release tasks message is to the new channel of described data base; Described data base receives described task message and stores; Whether described monitoring client monitor in real time storage task message in the database is triggered, and then judges whether to perform task events.
9. task system as claimed in claim 8, it is characterised in that include in the database:
Setting module, for creating new channel in the database, and for setting key name corresponding to the task message received and the second parameter field of the type set described task message of triggering according to described task message;
First information receiver module, is connected with described business end, for receiving the described task message that described business end sends;
Compression module, is connected with described information receiving module, and the described task message received is compressed into the key of correspondence;
Memory module, is connected with described setting module, described information receiving module and described compression module respectively, and described memory module is for storing key name corresponding to described task message, described task message and triggering the second parameter field of described task message;
First information sending module, is connected with described monitoring client and described memory module respectively, is used for the task that sends and triggers message extremely described monitoring client.
10. task system as claimed in claim 9, it is characterised in that described monitoring client includes:
Second information receiving module, is used for receiving described task and triggers message;
Screening module, is connected with described second information receiving module, and described screening module for triggering the task message of message relating according to preset keyword screening and described task;
Parsing module, is connected with described screening module, and described parsing module resolves the first parameter field in the task message that screening obtains;
Task execution module, with described parsing module, described task execution module performs the task events wherein comprised according to the analysis result of described parsing module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610010842.4A CN105677536A (en) | 2016-01-08 | 2016-01-08 | Implementing method for task messages and task system for implementing task messages |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610010842.4A CN105677536A (en) | 2016-01-08 | 2016-01-08 | Implementing method for task messages and task system for implementing task messages |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105677536A true CN105677536A (en) | 2016-06-15 |
Family
ID=56299566
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610010842.4A Pending CN105677536A (en) | 2016-01-08 | 2016-01-08 | Implementing method for task messages and task system for implementing task messages |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105677536A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107133741A (en) * | 2017-05-05 | 2017-09-05 | 东软集团股份有限公司 | Pending tasks processing method, device, readable storage medium storing program for executing and electronic equipment |
| CN108418894A (en) * | 2018-03-26 | 2018-08-17 | 威创软件南京有限公司 | A kind of Distributed Data Synchronization method based on push technologies |
| CN110750586A (en) * | 2019-10-12 | 2020-02-04 | 北京浪潮数据技术有限公司 | Operation information processing method and system of virtualization management platform |
| CN110837409A (en) * | 2018-08-16 | 2020-02-25 | 北京京东尚科信息技术有限公司 | Method and system for executing task regularly |
| CN111447258A (en) * | 2020-03-10 | 2020-07-24 | 广州华多网络科技有限公司 | Method, device and equipment for scheduling offline tasks and storage medium |
| CN111813845A (en) * | 2020-06-29 | 2020-10-23 | 平安国际智慧城市科技股份有限公司 | ETL task-based incremental data extraction method, device, equipment and medium |
| CN112463318A (en) * | 2020-11-17 | 2021-03-09 | 深圳市优必选科技股份有限公司 | Timed task processing method, device and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090037548A1 (en) * | 2002-05-14 | 2009-02-05 | Avaya Inc. | Method and Apparatus for Automatic Notification and Response |
| CN102982447A (en) * | 2012-10-31 | 2013-03-20 | 东莞宇龙通信科技有限公司 | Method and system of payment multi-channel prompting information |
| CN103209392A (en) * | 2012-01-16 | 2013-07-17 | 腾讯科技（深圳）有限公司 | Cross-process and multi-application massage pushing method and device |
| CN104410722A (en) * | 2014-12-19 | 2015-03-11 | 上海斐讯数据通信技术有限公司 | Method and system for communication of Web page window objects |
-
2016
- 2016-01-08 CN CN201610010842.4A patent/CN105677536A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090037548A1 (en) * | 2002-05-14 | 2009-02-05 | Avaya Inc. | Method and Apparatus for Automatic Notification and Response |
| CN103209392A (en) * | 2012-01-16 | 2013-07-17 | 腾讯科技（深圳）有限公司 | Cross-process and multi-application massage pushing method and device |
| CN102982447A (en) * | 2012-10-31 | 2013-03-20 | 东莞宇龙通信科技有限公司 | Method and system of payment multi-channel prompting information |
| CN104410722A (en) * | 2014-12-19 | 2015-03-11 | 上海斐讯数据通信技术有限公司 | Method and system for communication of Web page window objects |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107133741A (en) * | 2017-05-05 | 2017-09-05 | 东软集团股份有限公司 | Pending tasks processing method, device, readable storage medium storing program for executing and electronic equipment |
| CN108418894A (en) * | 2018-03-26 | 2018-08-17 | 威创软件南京有限公司 | A kind of Distributed Data Synchronization method based on push technologies |
| CN108418894B (en) * | 2018-03-26 | 2022-01-11 | 威创软件南京有限公司 | Distributed data synchronization method based on push technology |
| CN110837409A (en) * | 2018-08-16 | 2020-02-25 | 北京京东尚科信息技术有限公司 | Method and system for executing task regularly |
| CN110750586A (en) * | 2019-10-12 | 2020-02-04 | 北京浪潮数据技术有限公司 | Operation information processing method and system of virtualization management platform |
| CN111447258A (en) * | 2020-03-10 | 2020-07-24 | 广州华多网络科技有限公司 | Method, device and equipment for scheduling offline tasks and storage medium |
| CN111447258B (en) * | 2020-03-10 | 2023-04-07 | 广州方硅信息技术有限公司 | Method, device and equipment for scheduling offline tasks and storage medium |
| CN111813845A (en) * | 2020-06-29 | 2020-10-23 | 平安国际智慧城市科技股份有限公司 | ETL task-based incremental data extraction method, device, equipment and medium |
| CN112463318A (en) * | 2020-11-17 | 2021-03-09 | 深圳市优必选科技股份有限公司 | Timed task processing method, device and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105677536A (en) | Implementing method for task messages and task system for implementing task messages | |
| CN110310034B (en) | Service arrangement and business flow processing method and device applied to SaaS | |
| CN108874558B (en) | Message subscription method of distributed transaction, electronic device and readable storage medium | |
| CN104301436B (en) | Content to be displayed push, subscription, update method and its corresponding device | |
| CN111078504A (en) | Distributed call chain tracking method and device, computer equipment and storage medium | |
| CN108073625B (en) | System and method for metadata information management | |
| CN112527528A (en) | Data transmission method, device and storage medium based on message queue | |
| CN102664909A (en) | Re-establishing push notification channels via user identifiers | |
| CN112860451A (en) | Multi-tenant data processing method and device based on SaaS | |
| CN111309550A (en) | Data acquisition method, system, equipment and storage medium of application program | |
| CN111090423B (en) | Webhook framework system and method for realizing active calling and event triggering | |
| CN106230922A (en) | A kind of news subscribing method, message production unit and message reception units | |
| CN102955717A (en) | Message management equipment and method in distributed message processing system | |
| CN109639782A (en) | Message sends platform, method | |
| CN102981911A (en) | Distributed message handling system and device and method thereof | |
| CN106357466B (en) | A kind of internet product monitoring method and monitoring system | |
| US10237372B2 (en) | Scalable programming architecture for telecommunications devices | |
| CN112825525B (en) | Method and apparatus for processing transactions | |
| CN110798358B (en) | Distributed service identification method and device, computer readable medium and electronic equipment | |
| CN113645260A (en) | Service retry method, device, storage medium and electronic equipment | |
| CN106550002B (en) | paas cloud hosting system and method | |
| US10728323B2 (en) | Method and apparatus for operating infrastructure layer in cloud computing architecture | |
| CN113220480B (en) | Distributed data task cross-cloud scheduling system and method | |
| CN113626002A (en) | Service execution method and device | |
| CN110990213B (en) | Method and device for monitoring user logs of cluster environment in real time |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| AD01 | Patent right deemed abandoned |
Effective date of abandoning: 20190514 |
|
| AD01 | Patent right deemed abandoned |