From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) by hurricane.the-brannons.com (Postfix) with ESMTPS id B1A0D77D0D for ; Wed, 30 Dec 2015 04:25:47 -0800 (PST) Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-02v.sys.comcast.net with comcast id zoRr1r0012AWL2D01oSDuU; Wed, 30 Dec 2015 12:26:13 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-04v.sys.comcast.net with comcast id zoSC1r00K2MDcd701oSDZl; Wed, 30 Dec 2015 12:26:13 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20151229191702.GB1766@122oven.adamthompson.me.uk> <20151230120123.GA2471@122oven.adamthompson.me.uk> User-Agent: edbrowse/3.6.0+ Date: Wed, 30 Dec 2015 07:26:12 -0500 Message-ID: <20151130072612.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1451478373; bh=OB1UyHyHGfUc/9BDI9qsR4p4exCWVXauGZb200XXK8Q=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=cDn7BcKsEYba46A4mItzkNw+hLB2lpmCCi2v9sK0Vx38SX+kGCFjDnXtIYJ70+3RB TjM35TYiFkY9Xa2XyKUBr9HRwKuX9qLY32EMnh1/Cf+Nfl4r15H4HdJkbD0Y3KX3mx hz8w4KBXQDOhSz+mfd7YSZHVC3ovskmtEERvhf6XS3JNoC3JC3TnaNFjUnnDsO5gnb UFpLoK00zxBZqY7F9O3UgKy+bx7D+d1Yval6NTesHiv8hUVeg8tANsDZqnRuNNott7 U7bo64go+hPRnwaShfncFgbaUUCCSjKnV+rTcFcaIqTPKt7pRA0lsaJspjn1IEB1bp a9v+SfEHdjIlg== Subject: [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: Wed, 30 Dec 2015 12:25:47 -0000 > Ok, if I can I'd like to actually do some coding on edbrowse again, That would be awesome. I know you have a 9 to 5 and your time is limited. I've been able to put time in over the past year, tidy and dom representation and separate rendering of the page etc, and truly enjoyed it to be honest, but if you're ready for a turn I'll take a break for a bit and work on my 2 books or other things. edbrowse-curl is fine, we certainly use it for more than http: ftp, sftp, scp, etc, but I think it should be the same inage doing different things, as we discovered with edbrowse-js. Seems silly at first, you don't need all that other machinery, but we found that more and more stuff creeps in. The curl server will need information in the config file, so may as well parse that, and url management, and stringfile.c, and it needs to know all about plugins, even if it doesn't run the plugin directly it needs to know about it, and on and on and pretty soon you have 40 to 50 percent of the code so to ease distribution you may as well use the same image switching on argv[0]. Like main.c line 481, and then set whichproc = 'c'; (whichproc is e for edbrowse and j for javascript engine.) Just a thought - see how it plays out. Anyways, I'm happy to let you drive for a bit, and I'll step back to avoid conflicts, I think we're pretty much done with our experiments, separate handles do indeed share everything as expected, and I found socket.c, which you and Geoff can look at, so I'll submit just one more patch from Kevin, which implements synchronous xhr, and then I can just be in a bug fix minor updates mode for a while. I'll post another message when the xhr code is in, probably later today, and then you can have a whack at it. I may post some thoughts on messages to and from edbrowse-curl, if you don't mind, just to make sure we don't forget anything. That's probably the first step, a flow description of what kinds of messages / communication go back and forth. Cheers, Karl Dahlke