From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (unknown [IPv6:2602:4b:a4cb:c000::1]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id 58A8077D0D; Mon, 4 Jan 2016 16:37:54 -0800 (PST) From: Chris Brannon To: Adam Thompson Cc: Edbrowse-dev@lists.the-brannons.com References: <20151229191702.GB1766@122oven.adamthompson.me.uk> Date: Mon, 04 Jan 2016 16:38:32 -0800 In-Reply-To: <20151229191702.GB1766@122oven.adamthompson.me.uk> (Adam Thompson's message of "Tue, 29 Dec 2015 19:17:02 +0000") Message-ID: <8760z8c12v.fsf@mushroom.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] curl handles and general comms design X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 00:37:55 -0000 Adam Thompson writes: > To solve the parallel curl handles accessing cookie databases issue, > there's also the curl-shared interface. > I believe this can be used with the curl-multi interface since the curl-multi > interface is single-threaded so no need for mutexes etc. We're using that now, but with curl easy handles, rather than curl multi. I don't know what would be involved in moving over to curl multi. > What this all means I think is that, by combining both interfaces, > we should be able to create a single-threaded, essentially async, comms layer. The one problem is that you cannot share persistent connections across curl easy handles. Basically, you create a curl multi handle, and then add curl easy handles to it. So when would we create the individual curl easy handles? -- Chris