> No - the engine always tries to match exactly the 
> remote site, and will erase local files if remote 
ones 
> were erased - or missing. You can activate the 'do 
not 
> erase local files' option, but this won't work if 
the 
> file is still linked, and missing remotely (or in 
> error). I may add an option in the future however, 
> which will try to avoid that.. but this won't be 
quite 
> easy to implement (without breaking th cache)
> 

OK, i've tried to follow the code in this area but is 
isn't easy  :)  
...can you tell me: 
Is it guarenteed that the "transfer-status" callback 
(wrapper) is ALWAYS called BEFORE the original file is 
overwritten with the 404 message file? If i can rely 
on this behaviour, i can make a 'back-up' of any files 
with a 404 status before they are overwritten. So, can 
i rely on that?
many thanks,
john