Lessons for the Future of Event Processing

Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Lessons for the Future of Event Processing
# 1  
Old 11-01-2009
Lessons for the Future of Event Processing

by John Bates, Progress/ApamaOur academic vision for event processing in 1990sLessons learned from real business applications•* What did we omit from the academic vision?•* How much of the vision has come to pass so far?Architecture of a commercial event processing platformKiller applications of event processingPredictions for the event processing marketRead John Bates’ invited presentation at [...]

Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. What is on Your Mind?

Predict Future Outcomes in Our Event Prediction Market

Folks love to predict the future, so we have enabled predicting the future for members. So, please enjoy placing your Forum Bits predicting future outcomes in our new Event Prediction Market. Current events you can predict include science, technology, M&A and other global events: Oracle... (0 Replies)
Discussion started by: Neo
0 Replies
Login or Register to Ask a Question
Mail::SpamAssassin::Util::Progress(3pm) 		User Contributed Perl Documentation		   Mail::SpamAssassin::Util::Progress(3pm)

Mail::SpamAssassin::Util::Progress - Progress bar support for SpamAssassin SYNOPSIS
my $progress = Mail::SpamAssassin::Util::Progress->new({total => 100}); $msgcount = 0; foreach my $message (@messages) { # do something here $msgcount++; $progress->update($msgcount); } $progress->final(); DESCRIPTION
This module implements a progress bar for use in SpamAssassin scripts and modules. It allows you to create the progress bar, update it and print out the final results of a particular run. new public class (Mail::SpamAssassin::Util::Progress) new (\% $args) Description: Creates a new Mail::SpamAssassin::Util::Progress object, valid values for the $args hashref are: total (required) The total number of messages expected to be processed. This item is required. fh [optional] An optional filehandle may be passed in, otherwise STDERR will be used by default. term [optional] The module will attempt to determine if a valid terminal exists on the STDIN filehandle. This item allows you to override that value. init_bar public instance () init_bar() Description: This method creates the initial progress bar and is called automatically from new. In addition you can call init_bar on an existing object to reset the bar to it's original state. update public instance () update ([Integer $num_done]) Description: This method is what gets called to update the progress bar. You may optionally pass in an integer value that indicates how many messages have been processed. If you do not pass anything in then the num_done value will be incremented by one. final public instance () final ([Integer $num_done]) Description: This method should be called once all processing has finished. It will print out the final msgs per sec calculation and the total time taken. You can optionally pass in a num_done value, otherwise it will use the value calculated from the last call to update. perl v5.14.2 2011-06-06 Mail::SpamAssassin::Util::Progress(3pm)