Re: send-all='true' update REPORT mode and ra_serf

2011-02-17 Thread Mark Phippard
2011/2/17 Branko Čibej : > On 17.02.2011 21:43, Mark Phippard wrote: >> On Thu, Feb 17, 2011 at 3:35 PM, Ivan Zhakov wrote: >> >>> I'm looking to memory usage issues in svn update/export/switch in >>> ra_serf. And I come to question: what is the rationale of using >>> 'skelta' update REPORT mode,

Re: send-all='true' update REPORT mode and ra_serf

2011-02-17 Thread Branko Čibej
On 17.02.2011 21:43, Mark Phippard wrote: > On Thu, Feb 17, 2011 at 3:35 PM, Ivan Zhakov wrote: > >> I'm looking to memory usage issues in svn update/export/switch in >> ra_serf. And I come to question: what is the rationale of using >> 'skelta' update REPORT mode, and then sending many GETs/PROPF

Re: send-all='true' update REPORT mode and ra_serf

2011-02-17 Thread Mark Phippard
On Thu, Feb 17, 2011 at 3:35 PM, Ivan Zhakov wrote: > I'm looking to memory usage issues in svn update/export/switch in > ra_serf. And I come to question: what is the rationale of using > 'skelta' update REPORT mode, and then sending many GETs/PROPFINDs > instead of using send-all='true' mode and

send-all='true' update REPORT mode and ra_serf

2011-02-17 Thread Ivan Zhakov
Hi, I'm looking to memory usage issues in svn update/export/switch in ra_serf. And I come to question: what is the rationale of using 'skelta' update REPORT mode, and then sending many GETs/PROPFINDs instead of using send-all='true' mode and receiving all deltas and properties in one response? Doe