--- On Wed, 3/3/10, George Niculae <[email protected]> wrote:
>
> 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.
>
As a sample, one to be able to declare an event driven rule like:
on SBC save:
- replicate some_configfile
- restart service1
- restart service2
> 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)
_______________________________________________
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/
