Dav module temp files

Hello,
is there a technical reason why the WebDAV module (for PUTs) always
makes a temp file rather than use/honour memory buffer
(client_body_buffer_size)?

wbr
rr

Hello!

On Wed, Feb 29, 2012 at 01:55:42PM +0200, Reinis R. wrote:

Hello,
is there a technical reason why the WebDAV module (for PUTs) always
makes a temp file rather than use/honour memory buffer
(client_body_buffer_size)?

It will use memory buffer for intermediate data, but as it needs
file on disk anyway - data are always written to a file.

Maxim D.

On 02/29/2012 03:27 PM, Maxim D. wrote:

file on disk anyway - data are always written to a file.

Maxim D.
Just a tiny idea. (but perhaps this is already the case)
Ideally the temp file should be on the same file system than the target
file)
Otherwise the file has top be created twice.

Hello!

On Thu, Mar 01, 2012 at 02:47:40AM +0100, Gelonida N wrote:

It will use memory buffer for intermediate data, but as it needs
file on disk anyway - data are always written to a file.

Maxim D.
Just a tiny idea. (but perhaps this is already the case)
Ideally the temp file should be on the same file system than the target
file)
Otherwise the file has top be created twice.

Yes, and that’s why docs explicitly recommend using
client_proxy_temp on the same file system:

http://nginx.org/en/docs/http/ngx_http_dav_module.html#dav_methods

Maxim D.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs