[Edbrowse-dev] IPC, sooner?

[Karl Dahlke <eklhad@comcast.net>]

> 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