[asterisk-dev] asterisk curl function and socket keep alive

[Julian Lyndon-Smith]

See inline:


On 1 March 2011 19:53, Paul Albrecht <albrecht at glccom.com> wrote:
> On Tue, 2011-03-01 at 12:36 -0600, Terry Wilson wrote:
>> > I asked this question yesterday and didn't get much of a response so
>> > I'll try again ... Why is the keep alive socket option used for curl
>> > connection requests? The obvious disadvantage of keep alive is that the
>> > socket file descriptor is retained until the channel thread terminates.
>>
>> Don't start a new thread just because you didn't get the answer you want within a day. It isn't going to help. You also were talking with the author of func_curl. He gave you the reason "because it is the default" and suggested that the only reason it hasn't been changed is because no one had submitted a suitable patch to change the functionality.
>>
>
> I'm simply reporting a problem and haven't received an appropriate
> response. An appropriate response would be either: it's a feature or
> it's a bug. If it's the former than I expect a proper explanation, if
> it's the latter than I expect a fix.

Yikes.

"expect" ?

"would appreciate" is a so much better way of asking. I wouldn't
answer anyone that "expects" me to explain or fix the code I wrote
(especially if I wrote in in my own time for and donated it to you).

As you mentioned, you are simply reporting a problem. Not paying for a fix.

Julian

>
> What's a proper explanation? It's not "that's the way I wrote the code
> so that's the way it works." The author of the function should be able
> to give me an application scenario where the particular implementation
> makes sense from either an efficiency or usability perspective.
>
> As for submitting a patch, that seems rather pointless since the author
> is unable to state a reason for writing the code one way or another.
>
> And finally, simply complaining when someone points out a problem in
> code you're maintaining is awfully lame. If you don't have anything
> "technical" to contribute to the discussion why do you feel the need to
> respond?
>
>
>> Also, it looks like a weird combination of private conversation and mailing list posting. It gets a little confusing.
>>
>
> Since I wasn't asked to take the previous thread off list I assumed the
> responder forgot to cc back to the list. So I cc'ed the list in my
> responses.
>
>> Terry
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-dev
> --
> Paul Albrecht
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>



-- 
Follow "Ode To Politics" by HB Tasker at http://twitter.com/HBTasker