From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) by hurricane.the-brannons.com (Postfix) with ESMTPS id ECEE8787DC for ; Sun, 7 Dec 2014 15:04:28 -0800 (PST) Received: from resomta-ch2-11v.sys.comcast.net ([69.252.207.107]) by resqmta-ch2-04v.sys.comcast.net with comcast id Qn2K1p0052Ka2Q501n2jfJ; Sun, 07 Dec 2014 23:02:43 +0000 Received: from eklhad ([68.84.191.77]) by resomta-ch2-11v.sys.comcast.net with comcast id Qn2j1p00D1gep3001n2jMe; Sun, 07 Dec 2014 23:02:43 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Sun, 07 Dec 2014 18:02:43 -0500 Message-ID: <20141107180243.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=1417993363; bh=vmGNkupO+S+qvErGNVk0R6BqI+n+kqrAmFgquFC9hi0=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=ZTc7a8HrcelRPZ4MBvCKE87xVK2ccCYT+TSTt1I4Q/LkFwqJkAFinZqDH1UtCnK8k MSE9AUn/KUdK9ApJwwAGKcGgOu6nPO7ZlOGP4fl0jVun5ZJkg47KPgLYGbzFW/Hs2x ourmL+DxdhsBx8UIuQjpEOrK9GgJmr09LVYlUr9LLgOH5GKzrmCziYEeTE/se5ws9w hEO5aWJHaOl975e3UxnR8FM09T7llULB2cic9u8yoluPQEM6O0NCevgoxAUucyCrOn TzI0u8DSPXp0jC0On30hLQzGDmGVAs2dXMeGcxhPykyjdmKTcdhZwgEl4SxtRMqmz7 FIkxdJQbKnFgA== Subject: [Edbrowse-dev] IPC, sooner? X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 23:04:29 -0000 > Ok, that sounds like a good idea, though the js process's going to have to have > some sort of threading if we want to do ajax etc. right, but perhaps threading could come later, on the next increment. I'm thinking of pulling js to its own process, with an interprocess communication protocol, between edbrowse and js proc, that I would present here, first, for review, but all having the same functionality as today. Then of course we enhance it, and consider other engines, and such. > I'd also like to separate out downloading from the network somehow such that a > large download doesn't block the entire program. I think this is lots of work for little gain. Remember, everything asynchronous is a potential nightmare. I can download a 300 mb file and it just doesn't take very long. I think those features were developed when people were on dial-up connections. Really by the time I switch to another session to try to do something else, the file would already be downloaded. Maybe I'm spoiled by a good connection; but that's how it seems to me. And speeds will only increase. Karl Dahlke