> I'm thinking probably that each user would need their own edbrowse-curl,

If I, as a single user, could still have multiple instances
of edbrowse connecting to it, from different consoles,
accessing similar websites and sharing one cookie space,
then that makes sense and is fine.
/tmp/edbrowse directory could contain a file per user indicating
the process of edbrowse-curl running, if such is running,
/tmp/edbrowse/run-curl-user,
or spawn one otherwise, similar to the /var/run files in linux
though I don't think there is such a standard in windows
so we may as well use /tmp/edbrowse for this purpose on both OSs,
again keeping the code as much the same in both worlds.
This directory already exists and is used for temp files for plugins,
e.g. converting pdf to html in preparation for browse, etc etc.
Could also be used for temp files if we choose to use that mechanism
to pass the http data back to edbrowse.

> No, I think we just download the data,
> may be have a status message and then it's up to edbrowse what it does.

It could be  a personal preference, but I don't want it to work that way.
I don't want to sit there not knowing, and then later the download is done,
I want to see the progress dots as they happen, in real time,
otherwise why have them. I mean that's the whole point.
I also like to see the debug messages as they happen, in real time,
not spewing out at the end after download.
More than once edbrowse has been in an infinite loop,
despite our loop counter in http.c, an infinite redirection loop,
and I see that with db2, see the websites it is vectoring through,
or maybe the same site again and again, and I hit control c to stop it.
Anyways that's just an example - I want to see things as they happen.
It really isn't hard to do.

> > - Looks like a file you'll want to download, supply a file name or x to 
> > abort
> Again, I'd just download the data, if we want to pull it into memory then we
> can potentially do that, but mean while the data download carries on.

Small files just don't matter, and for big downloads you've
lost your flexibility here.
Maybe you don't have enough ram for that big iso image,
and maybe /tmp/edbrowse, or wherever you put it by default,
doesn't have room either.
It's on a basic windows drive like c: and you really have room on d:,
so curl asks you where you want to download it as soon as it gets the headers
and you direct it somewhere else.
It's a little more work to do it this way,
but not much more really, a few messages,
and that's how it works now,
and it will let some people do some things on some computers
that could not be done with an autodownload into a predefined place
and then figure it out later philosophy.

> on my internet connection I'd quite like to switch them off entirely tbh

That could be an easy toggle command.

> because, depending on the server,downloads happen either so fast I can't 
> count the dots or so
> slowly that having a random dot appearing is not very useful when I don't know
> the actual file size.

I guess I don't understand the second part.
Large downloads would happen in background, and you don't get the dots then 
anyways.

> Try counting how far through a 200 meg download you are in dot form,

It's easy, I just hit control w.
Again, that's my adapter, and maybe why I like the feature so much.

> content-length header) and the actual amount (to the byte preferably)
> that's actually been downloaded so I can see how long I have to wait.

sure, like a progress bar or percent indicator.
Actually I like that less but could be done and selected by the user,
dots or percent or quiet.


Karl Dahlke
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev

Reply via email to