can't flush I know why, but no fix

[T. Onoma]

I figured out why it won't work. i'm using 1.8's open_uri to retrieve the url with open(url). as soon as this executes everything stops until it downloads the whole file! it isn't a real IO. blah! that stinks. not i wonder if net/http and net/ftp do the same since that's what oprn_uri is based on. if so then means i might have to get down to the socket level just to do a progess reported download. frig'n wonderful!

If anyone knows of a better way, or a code snippet i can steal, Please let me know.

Thanks,
-t0

[Harry Ohlsen]

Hi tO,

T. Onoma wrote:

> I figured out why it won't work. i'm using 1.8's open_uri to retrieve the url with open(url). as soon as this executes everything stops until it downloads the whole file! it isn't a real IO. blah! that stinks. not i wonder if net/http and net/ftp do the same since that's what oprn_uri is based on. if so then means i might have to get down to the socket level just to do a progess reported download. frig'n wonderful!
>
> If anyone knows of a better way, or a code snippet i can steal, Please let me know.

Sorry, I don't know of any code snippets you could use as a starting point.

However, it might be worthwhile modifying open_uri to allow the asynchronous download and progress notification you want, and then submit a patch, so this can end up in the core code.

Cheers,

Harry O.

[Gavin Sinclair]

On Friday, November 14, 2003, 2:15:18 PM, T. wrote:

> I figured out why it won't work. i'm using 1.8's open_uri to
> retrieve the url with open(url). as soon as this executes everything
> stops until it downloads the whole file! it isn't a real IO. blah!
> that stinks. not i wonder if net/http and net/ftp do the same since
> that's what oprn_uri is based on. if so then means i might have to
> get down to the socket level just to do a progess reported download.
> frig'n wonderful!

> If anyone knows of a better way, or a code snippet i can steal, Please let me know.

net/ftp allows you to download a file a bit at a time. Dunno about
net/http.

Gavin

[T. Onoma]

> However, it might be worthwhile modifying open_uri to allow the asynchronous download and progress notification you want, and then submit a patch, so this can end up in the core code.

Thanks Harry! I took your advice. Its not quite asynchronous download, but what i did was add in a hook. So now you can do this:

require 'open_uri'
progress_proc = proc { |b| print "Downloaded #{b} bytes so far." }
open(url, progress_proc) { |f| print "Done" }

This of course will print many lines like:

Downloaded 1 bytes so far.
Downloaded 2 bytes so far.
Downloaded 3 bytes so far.
Downloaded 4 bytes so far.
Downloaded 5 bytes so far.
...
Done.

Not sure the exact count of bytes for each cycle. This really works well with Ruby/ProgressBar though (which moves back to the same line with each pass).

It probably could be made a tad more robust but I am pretty sure i covered all the base in the code. The this lib's in the distribution of Ruby, so how/who do i give the new version to now?

-t0

[Austin Ziegler]

On Fri, 14 Nov 2003 15:13:58 +0900, T. Onoma wrote:

>> However, it might be worthwhile modifying open_uri to allow the
>> asynchronous download and progress notification you want, and then
>> submit a patch, so this can end up in the core code.

> Thanks Harry! I took your advice. Its not quite asynchronous download,
> but what i did was add in a hook. So now you can do this:

...

> It probably could be made a tad more robust but I am pretty sure i
> covered all the base in the code. The this lib's in the distribution of
> Ruby, so how/who do i give the new version to now?

Create a patch file (diff -u, I think) and post it to ruby-core, along with
why you think it would be good to apply. (Not everyone on -core reads
-talk.)

-austin
--
austin ziegler * [email]austin@halostatue.ca[/email] * Toronto, ON, Canada
software designer * pragmatic programmer * 2003.11.14
* 07.57.22

[T. Onoma]

> Create a patch file (diff -u, I think) and post it to ruby-core, along with

> why you think it would be good to apply. (Not everyone on -core reads
> -talk.)

thanks austin,

i tried it, but core rejected my post saying i wasn't a member. perhaps i should [ANN] here to get it noticed?

-t0

[T. Onoma]

> i tried it, but core rejected my post saying i wasn't a member. perhaps i should [ANN] here to get it noticed?

hey i became member of core! and i even helped contribute. damn that feels good! :)

-t0

[Austin Ziegler]

On Sat, 15 Nov 2003 04:49:30 +0900, T. Onoma wrote:

> i tried it, but core rejected my post saying i wasn't a member. perhaps i
> should [ANN] here to get it noticed?

Send it directly to me and I'll post it to -core on your behalf.

-austin
--
austin ziegler * [email]austin@halostatue.ca[/email] * Toronto, ON, Canada
software designer * pragmatic programmer * 2003.11.14
* 16.57.02