Re: [fuse-devel] curlftpfs and streaming writes (was FUSE and lseek())

[Miklos S. <mi...@sz...>]

> i don't understand how a client application hanging in close() can send 
> an interrupt to FUSE.
> 
> i think the "old buffered writing" should be completely removed, and 
> only streaming writes continued with APPE

Yeah, APPE is good, because unlike REST, it should be supported on all
servers.  The only problem is if the file is extended or truncated on
the remote end, because then APPE may do the wrong thing.  But perhaps
we can live with this.

> or REST after a premature flush() should be used (because the
> premature flush might also occur in very big files).

In theory it might.  In practice, I don't know.

Miklos