Lieven Govaerts wrote:
> On Tue, Dec 22, 2009 at 11:58 AM, Philip Martin
> <philip.martin_at_wandisco.com> wrote:
>> Lieven Govaerts <svnlgo_at_mobsol.be> writes:
>>
>>> On Tue, Dec 22, 2009 at 10:18 AM, Philip Martin
>>> <philip.martin_at_wandisco.com> wrote:
>>>> Paul Querna <paul_at_querna.org> writes:
>>>>
>>>>> In either case, you would need somewhere to store them, and that is
>>>>> why I am writing the dev list: Where and how should a cache like this
>>>>> live?
>>>> How about with the DAV wcprops in the working copy?
>>> They will be gone in WC-NG if I followed the news correctly.
>> They will move, I wasn't aware we were going to get rid of them. They
>> cache the DAV version-urls, are we going to stop doing that?
>>
>
> You're right, it's the HTTPv2 protocol that stops using them. I was
> looking for a reference in the notes or the dev mailing lists, but
> can't find any. Maybe Mike can confirm this change.
Twisty passages. HTTPv2 doesn't use them any more. But Neon doesn't have
full HTTPv2 support. But some folks want to ditch Neon anyway and use only
Serf. But Serf still has laundry list of outstanding issues, not the least
of which is its glaring violation of the editor API usage rules (which has
already caused problems for some of our API-consuming users). But nobody is
working to fix Serf. But meanwhile, WC-NG still has "wcprops" support. But
it calls them "davprops" (though they should have been renamed "raprops"
since its the RA layer that uses them). But perhaps in light of the RA
situation we could get rid of them. But we could keep them around, instead.
But they won't work well for this application because they are keyed on
particular paths -- for capabilities exchange, you'd prefer to associate
your findings with the server and repository as a entity, not with each and
every particular path you happen to operate on. But that doesn't mean we
can't add something new to the mix. But anyway, that's the story.
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2009-12-22 15:33:15 CET