On Tue, May 8, 2012 at 4:09 PM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> On 05/08/2012 03:35 PM, Greg Stein wrote:
>> One question: the ordering of PROPFIND and GET. Do you know if that is
>> a requirement, or simply that you were preserving prior behavior?
> Upon reflection, it's probably not a hard requirement. In general, I
> suppose it's easier (and more efficient) to cache properties and stream
> contents while we drive an editor than the reverse, so that's probably why
> that ordering was chosen prior.
> I recall running into *some* problem when I tried to handle the contents
> inline (while processing the REPORT response). I can't recall for sure what
> that was, though (weekends are just fantastic amnesia drugs, sometimes!),
> but I think it boiled down to trying to figure out how to practically drive
> the editor partially, leaving the file baton open until some future
> pipelined PROPFIND request response was finally processed.
Cool. Thanks. Sounds like I may have some flexibility. Ev2 will
simplify a good bit of this, but we still need Ev1 support.
I have no schedule at all for this, as I'm more interested in an Ev2
commit editor. But thanks to you adding it to the tracker, we won't
Received on 2012-05-08 22:14:19 CEST