George wrote: > Since I've seen some issues raised due to replication trigger > and some fixes that broke other replication functionality -
Yes, I've noticed that this has been a problem area. > 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) Agreed, can you raise a Task JIRA? It would be great to have these triggers captured. As for what to implement... There have been some discussions about how to generalize replication. One goal would be to eliminate the need to trigger service restarts at all, but that's a long way off. Anything done for the interim would need to be clearly worth the effort and risk. What kinds of effort would this be? -Paul [email protected] _______________________________________________ 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/
