You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The callback is called by librsync. Thus there is no direct control over the parameters that are provided.
You could provide a kwarg to the patch function that allows the caller to provide their own callback, rather than using the default one. You could then provide your own buffering callback function.
It is possible the OS is buffering the read data already, obviating the need for actually going to disk, but YMMV.
On the other hand perhaps some changes could happen in librsync itself that would eliminate this reading pattern (algorithm optimizations). Of course librsync is old and mature so that is likely easier said (or typed) than done.
Activity
btimby commentedon Apr 30, 2014
The callback is called by librsync. Thus there is no direct control over the parameters that are provided.
You could provide a kwarg to the
patchfunction that allows the caller to provide their own callback, rather than using the default one. You could then provide your own buffering callback function.It is possible the OS is buffering the read data already, obviating the need for actually going to disk, but YMMV.
On the other hand perhaps some changes could happen in librsync itself that would eliminate this reading pattern (algorithm optimizations). Of course librsync is old and mature so that is likely easier said (or typed) than done.