You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Collins-Sussman <su...@collab.net> on 2004/12/17 21:49:40 UTC
hoping for a new neon release...
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:
1. Karl Fogel tells me that neon's trunk has a new API which fixes the
"control-c not interrupting neon" bug, which I believe is currently
filed as svn issue 1709. This has been a very long-lived annoyance for
lots of users. (Even our customers have complained about it!)
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.
Would you accept such a patch, Joe? (Assuming we worked out the
design, that is.)
Is there anything we can do to help get neon 0.25 out the door? Let us
know what we can do.
Many thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: hoping for a new neon release...
Posted by Ben Collins-Sussman <su...@collab.net>.
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
Re: hoping for a new neon release...
Posted by Joe Orton <jo...@redhat.com>.
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.
> 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)?
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
[neon] Re: hoping for a new neon release...
Posted by Erik Huelsmann <e....@gmx.net>.
[cc-ing neon list; I think it belongs there too]
> 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:
>
> 1. Karl Fogel tells me that neon's trunk has a new API which fixes the
> "control-c not interrupting neon" bug, which I believe is currently
> filed as svn issue 1709. This has been a very long-lived annoyance for
> lots of users. (Even our customers have complained about it!)
Heh! I just subscribed to the neon list last week to propose exactly the
above!
So count me in on producing any patches required on the neon or subversion
end to make this happen before Subversion 1.2 !
>
> 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.
>
> Would you accept such a patch, Joe? (Assuming we worked out the
> design, that is.)
>
> Is there anything we can do to help get neon 0.25 out the door? Let us
> know what we can do.
>
> Many thanks!
bye,
Erik.
--
NEU +++ DSL Komplett von GMX +++ http://www.gmx.net/de/go/dsl
GMX DSL-Netzanschluss + Tarif zum superg�nstigen Komplett-Preis!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
_______________________________________________
neon mailing list
neon@webdav.org
http://mailman.webdav.org/mailman/listinfo/neon
Re: hoping for a new neon release...
Posted by kf...@collab.net.
Ben Collins-Sussman <su...@collab.net> writes:
> 1. Karl Fogel tells me that neon's trunk has a new API which fixes
> the "control-c not interrupting neon" bug, which I believe is
> currently filed as svn issue 1709. This has been a very long-lived
> annoyance for lots of users. (Even our customers have complained
> about it!)
Note: I think it's actually the 0.25 dev branch that's important here
(but IIRC it does contain the fix).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: hoping for a new neon release...
Posted by Erik Huelsmann <e....@gmx.net>.
[cc-ing neon list; I think it belongs there too]
> 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:
>
> 1. Karl Fogel tells me that neon's trunk has a new API which fixes the
> "control-c not interrupting neon" bug, which I believe is currently
> filed as svn issue 1709. This has been a very long-lived annoyance for
> lots of users. (Even our customers have complained about it!)
Heh! I just subscribed to the neon list last week to propose exactly the
above!
So count me in on producing any patches required on the neon or subversion
end to make this happen before Subversion 1.2 !
>
> 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.
>
> Would you accept such a patch, Joe? (Assuming we worked out the
> design, that is.)
>
> Is there anything we can do to help get neon 0.25 out the door? Let us
> know what we can do.
>
> Many thanks!
bye,
Erik.
--
NEU +++ DSL Komplett von GMX +++ http://www.gmx.net/de/go/dsl
GMX DSL-Netzanschluss + Tarif zum superg�nstigen Komplett-Preis!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org