On Tue, 2010-01-19 at 11:55 -0600, [email protected] wrote: > I understand and like I said, just trying to find a way which doesn't > involve rebuilding sipx. I redundancy but I can live with it not being > perfect, just enough that users can tolerate the occasional problem.
The trouble with distributed database systems is (generally speaking) that if you don't *really* solve *all* the synchronization problems, you occasionally get problems. But the "problems" are "the database becomes completely nonfunctional until you manually fix the data structures", not "a user loses a voicemail message". If you construct a simple, effective solution to this problem, I'm sure that people here will want to hear about it. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
