Complex events: the “pickpocket event” on the Rome Metro
Paul Vincent’s Complex Event The best examples are always from real life.* Its hard to make up events like this…. and Complex Events they are! Paul describes the pattern of events that make up this “complex event”.* Actually it’s a good example of theft teamwork that happens everywhere, …. not just in the Eternal City. The puzzle I [...]
Hi,
Some sports predictions suggestions.
Although the Celtics are still playing the Heat. Just being optimistic that they will win. Otherwise, please change to Heat. (9 Replies)
log_mf_h(3erl) Erlang Module Definition log_mf_h(3erl)NAME
log_mf_h - An Event Handler which Logs Events to Disk
DESCRIPTION
The log_mf_h is a gen_event handler module which can be installed in any gen_event process. It logs onto disk all events which are sent to
an event manager. Each event is written as a binary which makes the logging very fast. However, a tool such as the Report Browser ( rb )
must be used in order to read the files. The events are written to multiple files. When all files have been used, the first one is re-used
and overwritten. The directory location, the number of files, and the size of each file are configurable. The directory will include one
file called index , and report files 1, 2, .... .
EXPORTS
init(Dir, MaxBytes, MaxFiles)
init(Dir, MaxBytes, MaxFiles, Pred) -> Args
Types Dir = string()
MaxBytes = integer()
MaxFiles = 0 < integer() < 256
Pred = fun(Event) -> boolean()
Event = term()
Args = args()
Initiates the event handler. This function returns Args , which should be used in a call to gen_event:add_handler(EventMgr,
log_mf_h, Args) .
Dir specifies which directory to use for the log files. MaxBytes specifies the size of each individual file. MaxFiles specifies how
many files are used. Pred is a predicate function used to filter the events. If no predicate function is specified, all events are
logged.
SEE ALSO gen_event(3erl) , rb(3erl)Ericsson AB stdlib 1.17.3 log_mf_h(3erl)
