On Dec 17, 2004, at 5:40 PM, Joe Orton wrote:
> On Fri, Dec 17, 2004 at 03:49:40PM -0600, Ben Collins-Sussman wrote:
>> Hey Joe Orton,
>>
>> I'm wondering if it's possible to get a new release of neon out the
>> door anytime soon... or at least in time for subversion 1.2. There
>> are two critical improvements I'm hoping for:
>
> I have one more API change I'm working on, hopefully I can get that
> done
> and a release out over the Christmas break.
Wonderful!
>
>> 2. I'm trying to teach ra_dav to issue LOCK and UNLOCK requests using
>> the nice pre-existing neon locking API. But the API doesn't allow me
>> to read or write custom headers in the request or response. I'd
>> rather
>> not reimplement all the LOCK code (and XML parsing) manually;
>> instead,
>> I was hoping that I could submit a patch to augment neon's API. I
>> guess it would be some sort of variant of ne_lock() and ne_unlock(),
>> one which allows access to either headers or the ne_request object.
>
> Headers for what, can you explain exactly what you're trying to do (to
> neon@webdav.org preferably)?
I already sent an email to neon@webdav.org earlier today, explaining
the problem. Maybe it needs to be modded through, since I'm not a
subscriber. Here it is, reprinted. Should we keep both svn and neon
lists cc'd, if we're going to discuss it?
------------
I'm trying to teach Subversion's dav layer to do LOCK & UNLOCK requests.
ne_lock.h looks like a wonderful API. But Subversion needs to both
send and receive custom HTTP headers in the request & response; it's
the only way to get a reasonable mapping between a Subversion lock_t
and a webdav lock_t.
Am I doomed? It looks like I'll have to reimplement all the logic of
ne_lock() manually -- including the XML response parser -- just so I
can send and receive custom headers.
Or is there some way I can get access to the ne_request object
directly, before and after the LOCK request is dispatched? Any clever
ideas?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 18 05:08:21 2004