> You implementation will probabely still have problems in > firewalled environements.
All servers should be able to reach each other by hostname/ip-address on the port specified. If firewalls are configured correctly then there is no issue. We also could provide a uicast property which overrides the active servers in the mmserver table. > in the furure i think we need to have only 1 connection > between 2 hosts and define in mmserver in what direction the > connection must be. > since you have only 2 thread I assume that for every change a > connection is build up or do you have 2 threads per host in > the network? For every change message a new connection is made to each server. The connection is not kept alive between the hosts. I took the most straightforward implementation. I didn't implement it for performance. > I was in favour of storing a list of changes in a changes builder. > so that in this example a server could poll the changes table > or even after a restart query the changes that happend during > the downtime. I don't see the advantage of a changes builder. The messages sent are only to inform another MMBase instance that something has changed and that his cache should be flushed. When you restart MMBase the caches are empty. Why should it poll the changes he does not have to apply to his cache? Nico
