[Edbrowse-dev] Messages to and from edbrowse-curl

[Karl Dahlke <eklhad@comcast.net>]

> Yeah that makes sense actually, but what do we do with the download
> in the meantime?
> I'm not sure if we should just pause waiting or not.

No I don't think that's good.
Servers will time out etc.
Nor do I think we should start writing to a temp file and move data around later.
I can tell you what we do today and hope that helps.
I analyze the headers as they come in and compare them
against standards and plugins etc.
If it is not text, and not something you know you want to download to play
as a plugin, say usually some kind of binary,
then I stop the download after the headers,
as though it were a HEAD call.
There's a curl command to stop the download gracefully.
Once I know where to send the data, I restart the call.
I get the headers and the data and into the file it goes
and it all works without trouble.

I imagine edbrowse-curl would analyze the headers as we do now,
and if a potential download, it sends the message back to edbrowse and stops.
Then edbrowse sends message back restarting the download
into the designated file,
thus the different messages: fetch generic and fetch into a named file.

Sure, I'll work on some different progress options,
including quiet, no progress indicators at all,
just the file size when done.
I'm happy to work on little features in parallel,
and there seems to be plenty of them.

cheers.

Karl Dahlke