28 Jan
2005
28 Jan
'05
1:44 p.m.
Juha Heinanen wrote:
Who is code maintainer for this part??
Greger V. Teigre writes:
Excellent! Will this code be available through CVS in the near future?
*** We all have this issue. It is my
understanding that
t_replicate: a) uses SIP messages b) uses a best-effort algorithm
(haven't looked at the code...) c) can be used between several
servers, but when you introduce a new server, you need to change
each server's ser.cfg
no you don't if you keep your server ip addresses in database and
have a fifo command to reload them each time there is a change. i
have started coding this, but is not ready yet. My suggestion
for a simple solution based on the discussion so far:
Extend t_replicate with a guaranteed mode of replication.
this indeed is a good thing to do. somebody mentioned that since ser fifo now has unix
domain support, it
would not be difficult to extend it to tcp support. that may be true
atleast for the person who did unix domain support and thus knows the
code. i guess fifo tcp support already is on iptel's long to-do list.
what comes to soap, i would prefer a solution that has an abstraction
layer and backends for both soap and xmlrpc, since not everyone of
fond of microsoft solutions.
I don't see soap as a microsoft solution, it's a bit bigger than that... ;-)
but I agree with you. It depends on your needs.
g-)