[Edbrowse-dev] One program Two processes

[Karl Dahlke <eklhad@comcast.net>]

> I'd go for UDP rather than TCP for local IPC,

Imagine one edbrowse-ht process, the one with the curl space,
that does all the http https and ftp fetches.
edbrowse connects to edbrowse-ht and says
"fetch this big http file and return it to me,
don't just download it I want it in memory, so return it to me."
edbrowse-ht pulls down a hundred meg file and sends it
back to edbrowse over socket,
but we need perfect fidelity here, we need the continuity
and certainty of the stream.
If we don't use tcp we'll have to reinvent most of it,
so we may as well use tcp, at least for this instance
and probably for most of our communications.
udp is fine for packet voice and such in that if you miss some packets you don't care,
it's barely a click in the sound, but here we need all the bits in
exactly the right order.

Karl Dahlke