You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Siegfried Goeschl <si...@it20one.at> on 2005/03/03 19:25:40 UTC

[Fulcrum] RFC - Contribution of a new Fulcrum Services ...

Hi folks,

I would like to contribute two additional Fulcrum services over the next 
few weeks if the Turbine/Fulcrum community is interested in it

+) fulcrum-notification-service
+) fulcrum-groovynotification-service

fulcrum-notification-service
=========================================================

The service is split into a fulcrum-notification-api-service and 
fulcrum-notification-impl-service.

A notification is either a command or an event.

    * a command is executed by the first command executor who's command
      acceptor evaluates to 'true'. The execution of a command yields to
      an result (might be null) or an exception.
    * an event is executed by the all event executor who's event
      acceptor evaluates to 'true'. The execution of an event may yield
      to an exception.

The services rely on the following assumptions

    * the notifications are untyped but expose a 'service', 'topic' and
      'item' field (String) similiar to Windows DDE
    * a notification is executed by an executor only if the associated
      acceptor evaluates to 'true'
    * a executor can register with mutiple acceptors to hold state
    * the execution of notifications are done in the same thread


fulcrum-groovynotification-service
=========================================================

This service provides an automatic mapping from events and commands to 
Groovy scripts executed by the Fulcrum Groovy Service


Thanks in advance

Siegfried Goeschl