Hg server replication

[Dustin Sallings]

On Nov 7, 2007, at 0:30, Wing Choi wrote:

> It does the reserve ahead when you push to the local replication
> server.  The advantage is that the local push is faster and is
> decoupled from the slower replay into primary sitting in another
> geo.  The repliation server in other locales then syncs from the
> primary at their own accord; and the users from each locale can
> pull the new txn from the own local replication server.  It saves
> the multitudes of folks in other locales from having to all trying
> to pull from a distance server.


	Then that's no different from a normal hg push, it sounds.

	How does SVK deal with conflicts when the servers are replicating  
changes?  Surely they come up.  How does SVK handle context?  i.e. how  
does it know that two changes that occurred at the same time in two  
different places were from the same base source?  My understanding is  
that it doesn't have globally unique identifiers.

-- 
Dustin Sallings