RETE Engines Must Forwards and Backwards Chain?!

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News RETE Engines Must Forwards and Backwards Chain?!
# 1  
Old 03-06-2010
RETE Engines Must Forwards and Backwards Chain?!

Tim Bass
03-06-2010 05:15 AM


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Checking status of engines using C-shell

I am relatively new to scripting. I am trying to develop a script that will 1. Source an executable file as an argument to the script that sets up the environment 2. Run a command "stat" that gives the status of 5 Engines running on the system 3. Check the status of the 5 Engines as either... (0 Replies)
Discussion started by: paslas
0 Replies

2. UNIX for Dummies Questions & Answers

Is it possible to extract a certificate chain?

Hi all! I wanted to look at the key length of a certificate chain we have. When I do the conventional export command using keytool I will only get the end user cert. keytool -export -alias aliasname -file filename.cer -keystore keystorename The above code will only give me the end user... (2 Replies)
Discussion started by: Keepcase
2 Replies

3. Shell Programming and Scripting

Find a sub chain in a file

Hello, I have a logfile from which i would to extract date and login information. (the goal is to find the inactive users). To extract the date, no problem. To extract the login, i'm stuck. I first extract lines which contains the logging-in information, i obtain different lines. Here... (2 Replies)
Discussion started by: Meldawa
2 Replies

4. Shell Programming and Scripting

How to chain some commands together

Hey, I am fiddling with a little script to kill a certain program if it freezes. Basically I want to do something like this: ps -A | grep firefox-bin | read -d ' ' pid kill $pid The problem lies when I pipe the output of grep into read. That part does not seem to work the way I want... (4 Replies)
Discussion started by: kermit
4 Replies

5. UNIX for Advanced & Expert Users

DNS forwards

I have to put in an Forward from an ip adress to another in our DNS , anyone know how to do that i pretty sure i have to put in somewhere in the named files but where? I tryed to put it in like an CNAME but it didn't work. any suggestions? /Nick (2 Replies)
Discussion started by: sajjan2
2 Replies

6. Shell Programming and Scripting

I dont want to know any search engines

I just want to know where I can download it on this website plz (1 Reply)
Discussion started by: memattmyself
1 Replies
Login or Register to Ask a Question
Mail::Milter::Chain(3pm)				User Contributed Perl Documentation				  Mail::Milter::Chain(3pm)

NAME
Mail::Milter::Chain - Perl extension for chaining milter callbacks SYNOPSIS
use Mail::Milter::Chain; my $chain = new Mail::Milter::Chain({ connect => &foo, ... }, ...); $chain->register({ connect => &bar, ... }); $chain->register({ connect => &baz, ... }); $chain->accept_break(1); use Sendmail::Milter; ... Sendmail::Milter::register('foo', $chain, SMFI_CURR_ACTS); DESCRIPTION
Mail::Milter::Chain allows multiple milter callback sets to be registered in a single milter server instance, simulating multiple milters running in separate servers. This is typically much less resource intensive than running each milter in its own server process. Any contained milter returning SMFIS_REJECT, SMFIS_TEMPFAIL, or SMFIS_DISCARD will terminate the entire chain and return the respective code up to the containing chain or milter server. Normally, a milter returning SMFIS_ACCEPT will remove only that milter from the chain, allowing others to continue processing the message. Alternatively, SMFIS_ACCEPT can be made to terminate the entire chain as is done for error results; see "accept_break()" below. A "Mail::Milter::Chain" is itself a milter callback hash reference, and can thus be passed directly to "Sendmail::Milter::register()" or another Mail::Milter::Chain container. IMPORTANT CAVEAT: Once this object has been registered with a parent container (a milter or another chain), DO NOT call "register()" on this object any longer. This will result in difficult to diagnose problems at callback time. METHODS
new([HASHREF, ...]) Creates a Mail::Milter::Chain object. For convenience, accepts one or more hash references corresponding to individual callback sets that will be registered with this chain. accept_break(FLAG) If FLAG is 0 (the default), SMFIS_ACCEPT will only remove the current milter from the list of callbacks, thus simulating a completely independent milter server. If FLAG is 1, SMFIS_ACCEPT will terminate the entire chain and propagate SMFIS_ACCEPT up to the parent chain or milter server. This allows a milter to provide a sort of "whitelist" effect, where SMFIS_ACCEPT speaks for the entire chain rather than just one milter callback set. This method returns a reference to the object itself, allowing this method call to be chained. register(HASHREF) Registers a callback set with this chain. Do not call after this chain has itself been registered with a parent container (chain or milter server). AUTHOR
Todd Vierling, <tv@duh.org> <tv@pobox.com> SEE ALSO
Mail::Milter, Sendmail::Milter perl v5.8.8 2004-02-26 Mail::Milter::Chain(3pm)