On Wed, Mar 3, 2010 at 2:44 AM, George Niculae <[email protected]> wrote: > Hi All, > > Since I've seen some issues raised due to replication trigger and some fixes > that broke other replication functionality - (for next release) I think that > would be good to consider / investigate a rule engine to handle this (could > be something proprietary or something already out there). Basically a > declarative event driven rule engine, easy to configure / maintain / enhance. > > A first step in this direction could be documenting sipXconfig replication > trigger mechanism that we already have in place (useful even without > considering the event engine approach) > > Any thoughts on this?
+1 We definitely need to improve the sipXconfig code in this area. We could build of a generic infrastructure based on Spring Event/Listener capabilities and reaction/Event Condition Action rules (http://en.wikipedia.org/wiki/Rule_engine#Types_of_rule_engines). Mircea > > George > > > > > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
