From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 1806778730 for ; Wed, 24 Dec 2014 00:11:56 -0800 (PST) Received: by mail-wg0-f41.google.com with SMTP id y19so10810589wgg.28 for ; Wed, 24 Dec 2014 00:09:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=8TXCGh5f6HpqylWmSzelTi5qDHpT4puGGz2ITUWXZMA=; b=TDMhHOfoJrT+4GKSgqYr3b0X/t/v6KzQfCM5Zcw7AFIEvERo3b0VaU2Uu6R+iHm/PQ +fc0teDFunCSfhanxfl0w3W64L84jOkpQ9Te4u0+9WLqmx3Yi4zh/YI8QnVxZYwv4FvW EL8VTTXXSEiKZCYACmaju1rBq89501M34ksm8j8TcvlZY9gl1etu4LAWI9SZZguUn2a5 Jgh5DLVzVk0DGu6AyVoy6xWeMATA8Do3HGx/TqVwhoEoqHH8rlKDIGtcnsGtvxExAvJh Y2gkE+2n2axYdGuhL06KYQz61T+Jd1V+Sc2gH5hCBPdupnceXhvkniYPU8hCrPPVTtyr oPFg== X-Received: by 10.180.206.47 with SMTP id ll15mr50347815wic.34.1419408587291; Wed, 24 Dec 2014 00:09:47 -0800 (PST) Received: from toaster.adamthompson.me.uk (toaster.adamthompson.me.uk. [2001:8b0:1142:9042::2]) by mx.google.com with ESMTPSA id t12sm17713187wju.19.2014.12.24.00.09.45 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Dec 2014 00:09:46 -0800 (PST) Date: Wed, 24 Dec 2014 08:09:43 +0000 From: Adam Thompson To: Karl Dahlke Message-ID: <20141224080943.GB10755@toaster.adamthompson.me.uk> References: <20141123175047.eklhad@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="U+BazGySraz5kW0T" Content-Disposition: inline In-Reply-To: <20141123175047.eklhad@comcast.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Edbrowse-dev@lists.the-brannons.com Subject: Re: [Edbrowse-dev] js engine process, version 1 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: Wed, 24 Dec 2014 08:11:56 -0000 --U+BazGySraz5kW0T Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 23, 2014 at 05:50:47PM -0500, Karl Dahlke wrote: > > it'd be nicer if the alert, prompt etc functions were done as part of t= he > > protocol, letting edbrowse handle user interaction I think. >=20 > Yeah I think so too, I was saving that for a future increment. Yeah, it may be worth doing sooner than later though, if only to make debug= ging easier. > > I don't see why this can't be done via ipc messages. >=20 > I may not know enough, but I don't think ipc messages play nice with > select, looking toward the day when we must monitor > many input streams at the same time, > many events coming in from many sources. > You can select on many file descriptors, as I do in my adapter and > other programs, but I don't think you can select on 4 file > descriptors and an ipc message queue. > If I'm wrong, we can switch from pipes to messages in the future, > if it makes sense to do so. > Probably not a big difference either way. I don't massively mind, and as for the select thing, it kind of depends on how portable we want to be. If we really want to be portable then no, the two don't play nice, but on linux, according to the documentation, they will actually work toget= her. I'm not sure how this'd be too much of a problem though, since each edbrowse will have it's own edbrowse-js (with associated message= queue), and each window within edbrowse (assuming we go down the process per window route) would share the message queue to the edbrowse-js process I suspect. We could also look at using the mq_notify function to make async operation = a bit easier and avoid the need to poll the message queue descriptors. Anyway, just thoughts on a future increment. Let's get what we have functio= ning first. Cheers, Adam. --U+BazGySraz5kW0T Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUmnTHAAoJELZ22lNQBzHOOxQH/jUQ3PoKbQyiM7h9pYjN/gEt D37HOkqKo46yp4gzxeO+lmKRrb3sp0CDKOcdtW9ltGKlRrva3aWGtdjJ2X7CEJGc OdPlmsMR+Wx29mvGnO/odtj5mHJ+iymVEodP50N3giIFKIRO03KF64eoiyOnE3Qs XI31F5Hs//opueOatlJnTMxJ9K6HG6EU1oJqISAeCFYRAtyJFGOke3dbthuRor1c qDFljl6YIlldxb3izmXjCP1ux1JCpz6nq+bPiDsWa/kLe9ZgrhSedQ/S/CbnjGLi OV3+baS5FwmJoDGCPVfn3a1KohQqu3KgnOLcw3OcX/29AXqK8CLnZqgWkT3L0Eg= =fXtb -----END PGP SIGNATURE----- --U+BazGySraz5kW0T--