[389-devel] Re: Future of nunc-stans

2019-10-22 Thread Rich Megginson
On 10/22/19 8:28 PM, William Brown wrote: I think turbo mode was to try and shortcut returning to the conntable and then having the blocking on the connections poll because the locking strategies before weren't as good. I think there is still some value in turbo "for now" but if we can bring

[389-devel] Re: Future of nunc-stans

2019-10-22 Thread William Brown
>> I think turbo mode was to try and shortcut returning to the conntable and >> then having the blocking on the connections poll because the locking >> strategies before weren't as good. I think there is still some value in >> turbo "for now" but if we can bring in libevent, then it diminishes

[389-devel] Re: Future of nunc-stans

2019-10-21 Thread Rich Megginson
On 10/21/19 4:42 PM, William Brown wrote: On 22 Oct 2019, at 07:28, Mark Reynolds wrote: On 10/9/19 10:00 PM, William Brown wrote: On 9 Oct 2019, at 19:55, Ludwig Krispenz wrote: Hi William, I like your radical approach :-) In my opinion our connection code is getting to complicated by

[389-devel] Re: Future of nunc-stans

2019-10-21 Thread William Brown
> On 22 Oct 2019, at 07:28, Mark Reynolds wrote: > > > On 10/9/19 10:00 PM, William Brown wrote: >>> On 9 Oct 2019, at 19:55, Ludwig Krispenz wrote: >>> >>> Hi William, >>> >>> I like your radical approach :-) >>> >>> In my opinion our connection code is getting to complicated by maintaini

[389-devel] Re: Future of nunc-stans

2019-10-21 Thread Mark Reynolds
On 10/9/19 10:00 PM, William Brown wrote: On 9 Oct 2019, at 19:55, Ludwig Krispenz wrote: Hi William, I like your radical approach :-) In my opinion our connection code is getting to complicated by maintaining two different implementations in parallel - not separated, but intermangled (and

[389-devel] Re: Future of nunc-stans

2019-10-10 Thread thierry bordaz
On 10/9/19 11:55 AM, Ludwig Krispenz wrote: Hi William, I like your radical approach :-) In my opinion our connection code is getting to complicated by maintaining two different implementations in parallel -  not separated, but intermangled (and even more complicated by turbo mode). So I a

[389-devel] Re: Future of nunc-stans

2019-10-09 Thread William Brown
> On 9 Oct 2019, at 19:55, Ludwig Krispenz wrote: > > Hi William, > > I like your radical approach :-) > > In my opinion our connection code is getting to complicated by maintaining > two different implementations in parallel - not separated, but intermangled > (and even more complicated by

[389-devel] Re: Future of nunc-stans

2019-10-09 Thread Ludwig Krispenz
Hi William, I like your radical approach :-) In my opinion our connection code is getting to complicated by maintaining two different implementations in parallel - not separated, but intermangled (and even more complicated by turbo mode). So I agree we should have only one, but which one ? I

[389-devel] Re: Future of nunc-stans

2019-10-08 Thread William Brown
> On 9 Oct 2019, at 09:18, Rich Megginson wrote: > > On 10/8/19 4:55 PM, William Brown wrote: >> Hi everyone, >> In our previous catch up (about 4/5 weeks ago when I was visiting >> Matus/Simon), we talked about nunc-stans and getting it at least cleaned up >> and into the code base. >> I've

[389-devel] Re: Future of nunc-stans

2019-10-08 Thread Rich Megginson
On 10/8/19 4:55 PM, William Brown wrote: Hi everyone, In our previous catch up (about 4/5 weeks ago when I was visiting Matus/Simon), we talked about nunc-stans and getting it at least cleaned up and into the code base. I've been looking at it again, and really thinking about it and reflectin