26 Sep
2004
26 Sep
'04
6:27 p.m.
Michael Shuler wrote:
Let's say I have 2 SER servers (ser1 and ser2).
Both save to the same MySQL
location table and both use t_replicate to let each other know about new
REGISTER's. Lets say ser1 gets a REGISTER from a client and then calls
t_replicate to send it over to ser2 and both call save("location").
Doesn't
that cause ser1 and ser2 to write the same record at about the same time to
MySQL? Is there any way to prevent doubling the number of database writes?
You can configure one of the ser's to do not use database at all for
storing contacts, which will do what you want - contacts will be saved
by the another ser, while t_replicate() will ensure that both of them
have a whole set at any moment of time.
-Maxim
Does anyone know what the replicate column is for in the location table?
----------------------------------------
Michael Shuler, C.E.O.
BitWise Communications, Inc. (CLEC) And BitWise Systems, Inc. (ISP)
682 High Point Lane
East Peoria, IL 61611
Office: (217) 585-0357
Cell: (309) 657-6365
Fax: (309) 213-3500
E-Mail: mike(a)bwsys.net
Customer Service: (877) 976-0711
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers