On 16 Dec 2010, at 3:31 PM, Mohammed Alli wrote: > Yes, I can understand the complexity of it. The command would have to > run on each msg so working it through a queue should be a faster method.
The message queue, just allows the processing to take place in the background but return a message to the user saying processing is happening and then provide them with the result when its done. If you don't use a message queue then the user will see a blank browser page until the system finishes processing which is not what users want. > Hmm, I wonder if selecting too many would slow things up drastically > affecting the performance of the system if done in real time. I do not think it would do that. > Maybe > being able to schedule this to run after hours might be something to > look at? Like selecting msg for spam retrain and saving it as a query > or something and then have cron pick it up at a selected time? We can add elements like this too but it would have to be a queuing mechanism too where you select the messages and schedule it to run at a certain time. Anyway for both these scenarios you need a message queuing system. -- Baruwa - www.baruwa.org _______________________________________________ Baruwa mailing list [email protected] http://lists.baruwa.org/mailman/listinfo/baruwa
