From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 961FD77D0D for ; Thu, 31 Dec 2015 18:42:58 -0800 (PST) Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-09v.sys.comcast.net with comcast id 0SjR1s0012Udklx01SjTy7; Fri, 01 Jan 2016 02:43:27 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-18v.sys.comcast.net with comcast id 0SjT1s0022MDcd701SjTMU; Fri, 01 Jan 2016 02:43:27 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20151129214611.eklhad@comcast.net> User-Agent: edbrowse/3.6.0+ Date: Thu, 31 Dec 2015 21:43:27 -0500 Message-ID: <20151131214327.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=1451616207; bh=EsA9SivWEdqmrp9vHsMaXNr5DvF6AR98qlJbZKSym8Y=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=EOL74UC47P81KBs29ENTNZoCN8CqMJCGb41sRCAFV+HQ2ZALTv2bTKuoymZ28Tt13 fvhmojFkEWIPrLk+JNoP7Lh5Qm89UUgDdx8fCN9W2WHGW9m3VsYGH9lRVC/8IggnWI +E33+ovLIuM+k2p3NmLYnYZpnxdtEIOq3bzWyNj9dNngLknXDbPj4fnkFKdwVGnGL/ G3q7UtkHXLq2CcSygSsEcV6SFM77huKKyeiVCA9kEGGYw/jXCIlKxjCQWe2+bWHHat 4J1C8eFm0FJcuUVG/JgnKGV6v7a3NGEczpawsz9utaGbSbt/3zgyI0+30S/lusy8Le BUXQd9uwCZkTA== Subject: [Edbrowse-dev] telling JS about allowXHR 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: Fri, 01 Jan 2016 02:42:58 -0000 > I was wondering how to get the allowXHR flag into javascript, Well this is a funny question, that I hadn't thought of before, but it has some real synergy with my post about edbrowse-curl messages back and forth. Remember I said that somehow updating variables in edbrowse, like, fmp fma, ftp mode active ftp mode passive, those sorts of variables have to propagate over to the curl server because they change its behavior. Well here we have one, the only one so far, that affects the behavior of js. When toggled in edbrowse, it has to propagate to the js engine. I think you were suggesting a counterpart variable, window.allowXHR$ or some such, that edbrowse could toggle when it toggled the variable in its own process space. But that doesn't work because it would have to tinker with such a variable in every open window in js, many buffers, each with a stack of web pages. Possible, but a bit impractical, nor does it generalize. I suspect we need a variable update message, update foo=bar which we already said we need for the curl server anyways. I'll give this some thought and put something in place; meantime you can continue to patch the other small items. Karl Dahlke