Sponsored Content
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News More on The Value of (Production) Rules Post 302261749 by Linux Bot on Tuesday 25th of November 2008 01:08:53 PM
Old 11-25-2008
More on The Value of (Production) Rules

Tim Bass
11-21-2008 02:43 PM
Paul Vincent of TIBCO wrote an outstanding post, The Value of (Production) Rules ... Paul correctly notes:
In summary, of course,* event-processing rules, event-driven rules, and rules for business decisions can all overlap, depending on the application.

By coincidence, I was reading an excellent paper recently, Reactive Rules on the Web. In this Springer-Verlag paper, the distinguished ILOG and University of Munich authors*(Bruno Berstel, Philippe Bonnard, Francois Bry, Michael Eckert and Paula-Lavinia Patranjan) say;
[Both] Event-Condition-Action (ECA) rules and production rules fall into the category of reactive rules, which are used for programming rule-based, reactive systems.

In other words, ECA rules and production rules are both a type of reactive rule, according to the literature.

Recently I read a blog post where the author hoped to distinguish between BRMS and CEP; citing a BRMS as a “production rule system” and CEP as a “reactive rule system”.** This distinction does not appear to work because production rules are also reactive rules, according to the literature.

If you are interested in event processing rules, I highly recommend Reactive Rules on the Web.



Source...
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dominant Unix in production?

What's the dominant Unix in production environment? Solaris or Linux? HP-UX and AIX have never been "dominant", while HP-UX is widely used in financial circles... Is Linux reallly where it's all going for major production environments running Oracle/SAP/whatever or will Solaris remain... (1 Reply)
Discussion started by: etc
1 Replies

2. UNIX for Dummies Questions & Answers

need help.. ! Production Env.

Hi ! I want to delete a softlink... with a name.. " -> ALCATEL " FYI:- lrwxrwxrwx 1 infomcm develop 32 Dec 3 2007 COX -> /wlsuite/om/cm/build/sandbox/COX lrwxrwxrwx 1 infomcm develop 33 Jul 21 05:52 WL10 -> /wlsuite/om-cm/build/sandbox/WL10 lrwxrwxrwx 1... (2 Replies)
Discussion started by: dashok.83
2 Replies

3. UNIX for Dummies Questions & Answers

To know the server which the production is pointing to?

Hi, How to know which server(Application or webserver) the production link or url is pointing to? Is there any command to get the server IP address? Thanks in advance. (3 Replies)
Discussion started by: venkatesht
3 Replies

4. BSD

Copying OpenBSD Kernel from a non production to production machine

Hi All, There are few OpenBSD 4.8 servers without compiler installed at my working place. However, sometimes there are some patches released for patching the kernel. My question is: Can I setup a non production OpenBSD 4.8 server as a test machine with compiler installed and use it to... (1 Reply)
Discussion started by: lcxpics
1 Replies

5. IP Networking

Production to DR switch

Hi, I have application server on IP 10.10.220.42 (Prod). When the Production goes down I wish to switch over all my application server's configuration files onto IP 10.10.220.45 (DR). The client is exposed to proxy apache http webserver running @ IP 10.10.220.30 Can you please suggest... (4 Replies)
Discussion started by: mohtashims
4 Replies
WWW::RobotRules(3)					User Contributed Perl Documentation					WWW::RobotRules(3)

NAME
WWW::RobotsRules - Parse robots.txt files SYNOPSIS
require WWW::RobotRules; my $robotsrules = new WWW::RobotRules 'MOMspider/1.0'; use LWP::Simple qw(get); $url = "http://some.place/robots.txt"; my $robots_txt = get $url; $robotsrules->parse($url, $robots_txt); $url = "http://some.other.place/robots.txt"; my $robots_txt = get $url; $robotsrules->parse($url, $robots_txt); # Now we are able to check if a URL is valid for those servers that # we have obtained and parsed "robots.txt" files for. if($robotsrules->allowed($url)) { $c = get $url; ... } DESCRIPTION
This module parses a /robots.txt file as specified in "A Standard for Robot Exclusion", described in <http://info.webcrawler.com/mak/projects/robots/norobots.html> Webmasters can use the /robots.txt file to disallow conforming robots access to parts of their web site. The parsed file is kept in the WWW::RobotRules object, and this object provides methods to check if access to a given URL is prohibited. The same WWW::RobotRules object can parse multiple /robots.txt files. The following methods are provided: $rules = WWW::RobotRules->new($robot_name) This is the constructor for WWW::RobotRules objects. The first argument given to new() is the name of the robot. $rules->parse($robot_txt_url, $content, $fresh_until) The parse() method takes as arguments the URL that was used to retrieve the /robots.txt file, and the contents of the file. $rules->allowed($uri) Returns TRUE if this robot is allowed to retrieve this URL. $rules->agent([$name]) Get/set the agent name. NOTE: Changing the agent name will clear the robots.txt rules and expire times out of the cache. ROBOTS.TXT The format and semantics of the "/robots.txt" file are as follows (this is an edited abstract of <http://info.webcrawler.com/mak/projects/robots/norobots.html>): The file consists of one or more records separated by one or more blank lines. Each record contains lines of the form <field-name>: <value> The field name is case insensitive. Text after the '#' character on a line is ignored during parsing. This is used for comments. The following <field-names> can be used: User-Agent The value of this field is the name of the robot the record is describing access policy for. If more than one User-Agent field is present the record describes an identical access policy for more than one robot. At least one field needs to be present per record. If the value is '*', the record describes the default access policy for any robot that has not not matched any of the other records. Disallow The value of this field specifies a partial URL that is not to be visited. This can be a full path, or a partial path; any URL that starts with this value will not be retrieved ROBOTS.TXT EXAMPLES The following example "/robots.txt" file specifies that no robots should visit any URL starting with "/cyberworld/map/" or "/tmp/": User-agent: * Disallow: /cyberworld/map/ # This is an infinite virtual URL space Disallow: /tmp/ # these will soon disappear This example "/robots.txt" file specifies that no robots should visit any URL starting with "/cyberworld/map/", except the robot called "cybermapper": User-agent: * Disallow: /cyberworld/map/ # This is an infinite virtual URL space # Cybermapper knows where to go. User-agent: cybermapper Disallow: This example indicates that no robots should visit this site further: # go away User-agent: * Disallow: / SEE ALSO
LWP::RobotUA, WWW::RobotRules::AnyDBM_File libwww-perl-5.65 2001-04-20 WWW::RobotRules(3)
All times are GMT -4. The time now is 10:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy