Be the first to post a text review of Complex Event Pattern Detector.. Rate and review a project by clicking thumbs up or thumbs down in the right column.

View all reviews

• Version 2.0 under development.

  We are currently designing and coding version 2.0 of ruleCore. The plans for 2.0 is more or less fixed but might be changed slightly. Here is a brief list of what to expect: Persistent storage of engine state in a mysql database. The state of the engine will be persistent and will survive crashes and normal shutdowns. The engine state is automatically managed and the user will not need to do anything to enable it expect configuring a mysql database. Windows portability for the engine. The source code of the engine contains a few annoying (as pointed out by many people) lines of code that won't run on Windows. These will be replaced by portable code for 2.0 Better startup and shutdown behavior. Thanks to a component architecture and the persistent storage of state, the engine will behave nicely even when killed in the most brutal way. Component plug-in architecture. A completely new component architecture is introduced in 2.0. Components can be written in Python to begin with and probably in C++ and Java in the future. Users can write their own components to extend the engine in a structured way. The component framework takes care of component startup, shutdown and persistence. Support for running several engine instances on one server. There is one annoying TCP/IP port hard coded, once removed several engine instance can be started on the same server. Support for distributed setup. We received a very interesting contribution of code for using engines on several engines and connecting them together. Some new situation detection nodes. There will be a new sequence node for detecting special sequences and a tempo node detecting when events enter too fast or too slow. Pass through of user defined data.

  posted by marcorc 1903 days ago

• ruleCore 1.1beta3 released.

  This is a bugfix release and documentation update.

  posted by marcorc 1984 days ago

• Translators: Manual as OpenOffice doc

  Now it is possible to download the ruleCore Users Guide in OpenOffice format. This is intended for those who would like to work on a translation of the manual. Others may continue to use the pdf users guide. The guide can be downloaded here: http://www.rulecore.com/support/documents/usersguide.sxw

  posted by marcorc 1990 days ago

• ruleCore 1.1beta2 released

  1.1beta2 is now released. It contains a couple of small fixes. You should use 1.1beta2 instead of 1.0 as it fixes a number of problems in 1.0. The documentation has been updated to reflect reality much better.

  posted by marcorc 1998 days ago

• ruleCore 1.1beta1 released

  This release fixed a number of bugs in the Designer gui and the Engine. The 1.1 release is focused on making things easier to use and harder to break. The concept of "event selector" is introduced. An event selector lets you select which events that should take part in the situation detector of each rule instance. Now events can be generated when an situation is detected (before and independent of if the rule triggers its action) or when a situation will never be detected. Initial support is added for Zope based on the ZRuleCore product on www.zope.org. Zope support is not tested att all yet.

  posted by marcorc 2009 days ago

• File released: /rulecore/1.0/rulecore-1.0-0.src.tgz

  posted 2089 days ago

• File released: /rulecore/1.0/rulecore-1.0-0.i386.rpm

  posted 2089 days ago

• rulecore 1.0 file released: rulecore-1.0-0.i386.rpm

  posted 2090 days ago

• rulecore 1.0 file released: rulecore-1.0-0.src.tgz

  posted 2090 days ago

• Code committed

  Anonymous committed patchset 1 of module CVSROOT to the Complex Event Pattern Detector. CVS repository, changing 11 files

  posted by nobody 2091 days ago