HFS+ resource forks: WIP patch included

John Van Essen vanes002 at umn.edu
Fri Mar 12 10:39:47 GMT 2004

On Wed, 10 Mar 2004, Wayne Davison <wayned at samba.org> wrote:
> On Wed, Mar 10, 2004 at 01:11:35PM -0500, D Andrew Reynhout wrote:
>> but I'm less clear on
>> why (it appears) that *both* sides sort the flist.
> This is because the flist gets sent as it is created, so it is sent
> unsorted.  Without this rule it would be necessary to wait until the
> list had been fully read from disk and sorted before it was transferred,
> making the use of time much less optimal (it's better to have the disk
> I/O and network I/O overlap rather than be consecutive).

The How Rsync Works document at:



  The first thing that happens once the startup has completed
  is that the sender will create the file list. If there are
  many files it may take a while for this to happen. This is
  the most common point for communications timeouts to occur.

  After the complete file list has been created it is then sent
  to the receiver in a network optimised way. 

So that needs to be updated to reflect current operation.

And, JW, when is this document going to go on the rsync site?

Can it be maintained via CVS?

One HTML suggestion - in the Processes and Roles table, you
used  valign="top"  in the <table> tag.  You need to use it in
all the <tr> tags to get the first 2 columns valigned that way.


More information about the rsync mailing list