On Sat, Jul 22, 2017 at 10:49:40PM -0400, Karl Dahlke wrote: > This is either for fun, or for testing, or for the future. I'm not sure. > > export JS1=on
Ok, so how're we going to do all the async js stuff we'll have to start doing properly soon? Tbh I'm not sure how much I'm attached to the multiple process idea other than it means js can go pop and we don't... but we *need* to sort out async js soon. Unfortunately websites are becoming increasingly reliant on ajax being genuinely async and that's before we get to websockets etc. With 2 processes it means that we can start with a simple interface with pipes and select as now. With 1 we'll need to do thread-safe programming to make this fly properly. It's not impossible but we'll have to make a bunch of changes to make the existing code properly thread-safe to make that work, or have some way to run duktape in a mode where it only does a certain amount of instructions and use select/poll/some event loop to allow io, comms and js to work together... Honestly I'm not sure what the right design is yet. I've been, unfortunately, rather busy and unable to do much on edbrowse recently so I'm still catching up with things. That being said, this variable, plus the fact that we've made the switch to duktape (well done for that, sorry I ran out of time to help) gives us a mechanism to may be play with some sort of different model for running js. Cheers, Adam. _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
