On 3/19/15, Andy Bradford <amb-fos...@bradfords.org> wrote:
> Thus said Richard Hipp on Wed, 18 Mar 2015 13:41:31 -0400:
>
>> (The SERVERCODE is  an historical artifact that is no  longer used for
>> anything and can be safely ignored.)
>
> I did  not realize that  it was no longer  used; does sync.wiki  need an
> update? Currently it says:
>
>     The servercode argument is the repository ID for the client. The
>     server  will  only  allow  the transaction  to  proceed  if  the
>     servercode is different from its own servercode. This prevents a
>     sync-loop.
>

Probably that should be updated.

I original put in the server code to prevent sync loops.  But that
cause problem when people would scp the repo up to the server, then
try to sync local to server.  It required that the server code be
manually changed after the scp.  Which was annoying.  So I disable the
server-code checking to see if it would cause any "sync-loop"
problems, and it did not.  So I left it disconnected.  That was many
years ago.  
https://www.fossil-scm.org/fossil/timeline?y=ci&c=469efd6a7ce8ba441b7c

-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to