In some cases, you may want to use Filespooler to send the data from one machine to many others. An example of this could be using gitsync-nncp over Filespooler where you would like to propagate the changes to many computers.
This setup is quite easy with Filespooler. All you need to do is transport the queue files to each destination. I use NNCP’s multicast areas support (see Using Filespooler over NNCP for details about NNCP with Filespooler) for this, but you could really use any transport.
Since each receiving machine maintains its own queue and sequence file, ordering is preserved on each one.
For a different topology, see Many-To-One with Filespooler.
Links to this note
Filespooler is a way to execute commands in strict order on a remote machine, and its communication method is by files. This is a perfect mix for Syncthing (and others, but this page is about Filespooler and Syncthing).
Filespooler lets you request the remote execution of programs, including stdin and environment. It can use tools such as S3, Dropbox, Syncthing, NNCP, ssh, UUCP, USB drives, CDs, etc. as transport; basically, a filesystem is the network for Filespooler. Filespooler is particularly suited to distributed and Asynchronous Communication.