|
|
Sponsored Content
Special Forums
News, Links, Events and Announcements
Complex Event Processing RSS News
On external and internal decision in event processing
Post 302259163 by Linux Bot on Monday 17th of November 2008 12:10:04 PM
11-17-2008
On external and internal decision in event processing
2008-11-17T12:33:00.007+02:00
This picture shows the external and internal parts of an house (not mine...). I am at home now in a day off (have to finish 10 days by the end of the year so taking them one by one), have to travel to Tel-Aviv on some matter, but meanwhile spending a few minutes in Blogland. My last posting has dealt with event processing and decisions.
James Taylor has answered in saying that decisions may be triggered by events, but the decision itself is not dependent on the events. I think that we are on the same wavelength here, so let me make some comments in my terminology. In the early days of active databases there has been a distinction between its use for "internal applications" that helps to manage the DBMS system itself, i.e. manage transactions, and "external applications" which belong to the business domain. Likewise, we can observe internal and external decisions in processing events. The event processing network consists of a lot of internal decisions -- decision of where to route events, decision of which events will be filtered out, decision on when context should expire, decision on whether a pattern has been detected, a decision what to do when a pattern is detected and more. This are all internal decisions that help moving the EPN towards its edges. The interface between the EPN and its consumers occur at that edges. In the edge there are several possibilities:
1. The EPN notifies the consumer about the event that flows in the edge, and the consumer decided manually what should be done, or can manually run any decision process
2. The EPN triggers a decision rule, the decision is a function of the event that triggered it, in this case the EPN triggers an external decision.
3. The EPN triggers a decision, but the decision is not a function of the content of the triggering event, this I assume is the case that James Taylor has referred to.
Source...
This picture shows the external and internal parts of an house (not mine...). I am at home now in a day off (have to finish 10 days by the end of the year so taking them one by one), have to travel to Tel-Aviv on some matter, but meanwhile spending a few minutes in Blogland. My last posting has dealt with event processing and decisions.
James Taylor has answered in saying that decisions may be triggered by events, but the decision itself is not dependent on the events. I think that we are on the same wavelength here, so let me make some comments in my terminology. In the early days of active databases there has been a distinction between its use for "internal applications" that helps to manage the DBMS system itself, i.e. manage transactions, and "external applications" which belong to the business domain. Likewise, we can observe internal and external decisions in processing events. The event processing network consists of a lot of internal decisions -- decision of where to route events, decision of which events will be filtered out, decision on when context should expire, decision on whether a pattern has been detected, a decision what to do when a pattern is detected and more. This are all internal decisions that help moving the EPN towards its edges. The interface between the EPN and its consumers occur at that edges. In the edge there are several possibilities:
1. The EPN notifies the consumer about the event that flows in the edge, and the consumer decided manually what should be done, or can manually run any decision process
2. The EPN triggers a decision rule, the decision is a function of the event that triggered it, in this case the EPN triggers an external decision.
3. The EPN triggers a decision, but the decision is not a function of the content of the triggering event, this I assume is the case that James Taylor has referred to.
Source...
|
|
4 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I am running a bash script under linux which first defines an CA-array like
j=0
num1=120.00
num2=10.00
until
do
CA='echo $num1 + $j*$num2'
j=$
done
within the later awk section of this same script I want to read data from a file. If the value of the second column is... (3 Replies)
Discussion started by: MotAah
3 Replies
2. Shell Programming and Scripting
Hi there, I'm new to shell scripting and need some help if possible?
I need to create a shell script (.sh) to run as a cron job on an ubuntu linux server to connect to an external sftp sites directory using credentials (which I have) and then download to our internal ftp server and then copy... (3 Replies)
Discussion started by: ghath
3 Replies
3. Red Hat
How to check whether the disk in linux machine are internal or external ( from nas or san). How to identify internal(local) and external disks. Following are some details of my server. Thanks.
#df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 15G 3.5G 10G... (2 Replies)
Discussion started by: salmanraza
2 Replies
4. UNIX for Advanced & Expert Users
Morning,
I'm trying step up my scripting game .. :rolleyes::confused::D
Is there a way to do the replacement with an or without using an external command ?
I did try but no joy.
var=${var//\(|\)/}
#!/bin/bash
var="lulus.UbiRwidgets.com (10.1.1.1)"
var=${var//\(/}... (5 Replies)
Discussion started by: popeye
5 Replies
LEARN ABOUT DEBIAN
webcheck
webcheck(1) User Commands webcheck(1) NAME
webcheck - website link checker SYNOPSIS
webcheck [OPTION]... URL DESCRIPTION
webcheck will check the document at the specified URL for links to other documents, follow these links recursively and generate an HTML report. -i, --internal=PATTERN Mark URLs matching the PATTERN (perl-type regular expression) as an internal link. Can be used multiple times. Note that the PATTERN is matched against the full URL. URLs matching this PATTERN will be considered internal, even if they match one of the --external PATTERNs. -x, --external=PATTERN Mark URLs matching the PATTERN (perl-type regular expression) as an external link. Can be used multiple times. Note that the PATTERN is matched against the full URL. -y, --yank=PATTERN Do not check URLs matching the PATTERN (perl-type regular expression). Like the -x flag, though this option will cause webcheck to not check the link matched by regex whereas -x will check the link but not its children. Can be used multiple times. Note that the PATTERN is matched against the full URL. -b, --base-only Consider any URL not starting with the base URL to be external. For example, if you run webcheck -b http://www.example.com/foo then http://www.example.com/foo/bar will be considered internal whereas http://www.example.com/ will be considered external. By default all the pages on the site will be considered internal. -a, --avoid-external Avoid external links. Normally if webcheck is examining an HTML page and it finds a link that points to an external document, it will check to see if that external document exists. This flag disables that action. --ignore-robots Do not retrieve and parse robots.txt files. By default robots.txt files are retrieved and honored. If you are sure you want to ignore and override the webmaster's decision this option can be used. For more information on robots.txt handling see the NOTES section below. -q, --quiet, --silent Do not print out progress as webcheck traverses a site. -d, --debug Print debugging information while crawling the site. This option is mainly useful for developers. -o, --output=DIRECTORY Output directory. Use to specify the directory where webcheck will dump its reports. The default is the current directory or as specified by config.py. If this directory does not exist it will be created for you (if possible). -c, --continue Try to continue from a previous run. When using this option webcheck will look for a webcheck.dat in the output directory. This file is read to restore the state from the previous run. This allows webcheck to continue a previously interrupted run. When this option is used, the --internal, --external and --yank options will be ignored as well as any URL arguments. The --base-only and --avoid-external options should be the same as the previous run. Note that this option is experimental and it's semantics may change with coming releases (especially in relation to other options). Also note that the stored files are not guaranteed to be compatible between releases. -f, --force Overwrite files without asking. This option is required for running webcheck non-interactively. -r, --redirects=N Redirect depth. the number of redirects webcheck should follow when following a link. 0 implies to follow all redirects. -u, --userpass=URL Specify a URL with username and password information to use for basic authentication when visiting the site. e.g. http://test:secret@example.com/ This option may be specified multiple times. -w, --wait=SECONDS Wait SECONDS between document retrievals. Usually webcheck will process a url and immediately move on to the next. However on some loaded systems it may be desirable to have webcheck pause between requests. This option can be set to any non-negative number. -v, --version Show version of program. -h, --help Show short summary of options. URL CLASSES
URLs are divided into two classes: Internal URLs are retrieved and the retrieved item is checked for syntax. Also, the retrieved item is searched for links to other items (of any class) and these links are followed. External URLs are only retrieved to test whether they are valid and to gather some basic information from them (title, size, content-type, etc). The retrieved items are not inspected for links to other items. Apart from their class, URLs can also be considered yanked (as specified with the --yank or --avoid-external options). The URLs can be either internal or external and will not be retrieved or checked at all. URLs of unsupported schemes are also considered yanked. EXAMPLES
Check the site www.example.com but consider any path with "/webcheck" in it to be external. webcheck http://www.example.com/ -x /webcheck NOTES
When checking internal URLs webcheck honors the robots.txt file, identifying itself as user-agent webcheck. Disallowed links will not be checked at all as if the -y option was specified for that URL. To allow webcheck to crawl parts of a site that other robots are disallowed, use something like: User-agent: * Disallow: /foo User-agent: webcheck Allow: /foo ENVIRONMENT
<scheme>_proxy Proxy url for <scheme>. REPORTING BUGS
Bug reports shoult be sent to the mailing list <webcheck-users@lists.arthurdejong.org>. More information on reporting bugs can be found on the webcheck homepage: http://arthurdejong.org/webcheck/ COPYRIGHT
Copyright (C) 1998, 1999 Albert Hopkins (marduk) Copyright (C) 2002 Mike W. Meyer Copyright (C) 2005, 2006, 2007, 2008, 2009, 2010 Arthur de Jong webcheck is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The files produced as output from the software do not automatically fall under the copyright of the software, unless explicitly stated otherwise. Version 1.10.4 Sep 2010 webcheck(1)