From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2001:558:fe21:29:69:252:207:41; helo=resqmta-ch2-09v.sys.comcast.net; envelope-from=eklhad@comcast.net; receiver= 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 DE58B7A681 for ; Sun, 6 Aug 2017 22:53:03 -0700 (PDT) Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id eaysdTTIJ4JGmeaz1d9BPR; Mon, 07 Aug 2017 05:53:43 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1502085223; bh=rkqVAjCtj2MJtIXzh7PUfouz5ehchzRc3QHwGNsDhOg=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=Z2z9xqsBitYvAi1gtOI0Aoe4QzinmbP51Md3ptwRI3xLpE+9rCA61TrCKtZ3vMqaE D8sV9xKJGxTniTB3bsFA+eDvvj0u5sIkOUDDsxFy2Xm0n6ZOCXIrK0zxPytLIVYzLj nk625ul6yBCwXBItDNFuAl5TQqlzkMDGnfdcuGJTAtapqQ+SpqyGuYQwWDyCpjoNTh flmY1TS08SxR8iPAlfXzAp/wI197J8r3VPdMr4T2waYxXyFLWJ08Gl7HNDV+IAExTE N6F92/QAD1PQOlMsBX/2D6e32SY/MFDLhGJswcLHDi2iQ3hF/jxP8dXbP7CETDhj8T p92XVeGuaQzdA== Received: from unknown ([IPv6:2601:408:c301:784d:21e:4fff:fec2:a0f1]) by resomta-ch2-04v.sys.comcast.net with SMTP id eaz0dMl4kN1TYeaz0dCtDS; Mon, 07 Aug 2017 05:53:43 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20170705184007.eklhad@comcast.net> User-Agent: edbrowse/3.7.0+ Date: Mon, 07 Aug 2017 01:53:42 -0400 Message-ID: <20170707015342.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=nextpart-eb-849981 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfKaaeNp1W/pCkJkdCZMGlC8X7ZNea+H8iZIt0TlGNdISldc3f1FcaicuCgwNgu9viWycETVilKE1wVLdybh076y/lOPnJEHZh5GXB8jdz7ZsuDnDZdr9 60Sz7q6yzC1XHFOHuotJhLFkBbsh2zm74xEMVavc5KFwci+zjfYjIN+c Subject: [Edbrowse-dev] Frame AutoExpansion X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.24 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2017 12:58:43 -0000 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --nextpart-eb-849981 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sure .. option 1 wasn't really an option, I just put it out there. I think my last idea is quite doable, and has all the benefits of = saving resources when the frames are not needed, and expanding them = under the covers when they are. It does push us towards a one process design, but I think other factors = do as well. Try as we might, it's nearly impossible to keep all the cookies in sync = as two processes both fetch html pages from the same website. 98% of the time that won't matter, but when one fetch sets a cookie and = the second fetch (in the other process) doesn't work properly unless = that cookie is present, well, some of this we manage, like when js sets = the cookie via document.cookie, but when cookies ride in on http = headers through curl under the covers, well as I say it's really hard to handle every case. This an other = concerns go away with one process and one curl space, so we might be = going that direction anyways. I'm currently changing messages to simple function calls, at least for = JS1, which will make it easier to do recursive and reentrant things. This sounds easy but not quite: the messaging allows for some nice = debugging because I can log each message back and forth, without messages I have to put the same debug statements around various = function calls. And I do want the debug features as they are today, very useful. It's not hard, just lots of details. Karl Dahlke --nextpart-eb-849981--