Sorry - not sure if I've misunderstood your answer or if you didn't get
my suggestion. If the former then apologies in advance for banging on
and I'll go back to quietly lurking :-)
I'm suggesting a method for making the user's browser display a progress
bar for us while a split-file download progresses to private download
area within Fred:
- User requests splitfile download, e.g. by clicking on link within
FProxy
- Fred/FProxy reports dummy filesize to browser of, say, 100k
- Meanwhile Fred downloads splitfile in background, in whatever
block order, to private file owned by Fred
- as background download progresses, FProxy returns garbage to
browser at a bitrate of, e.g., 1k per 1-percent split-file successfully
downloaded
- Browser displays percentage bar for us based on its view of how
complete the 100k dummy download is
- When split-file complete, FProxy redirects browser to a special
link, that when navigated to, streams the downloaded splitfile from
Fred's private file
-- jeek
Matthew Toseland wrote:
>Eek.
>
>Square peg, round hole.
>
>We have to download to disk, this is the only reasonable option.
>However, we can do it inside Fred.
>
>
>On Wed, Aug 31, 2005 at 08:32:15PM +0100, junk at giantblob.com wrote:
>
>
>>What about this for a glorious kludge?
>> large file downloads from fproxy actually trigger the 'download' of
>>a modest size dummy file, the progress of which is matched to the
>>progress of the actual split-file download - this provides the users'
>>standard browser UI/feedback for a download
>> when the download is 99% complete, fproxy redirects the browser to a
>>link to the actual download, which then completes instantly
>>
>>-- jeek
>>
>>Colin Davis wrote:
>>
>>
>>
>>>I just fail to see what an applet gains that can't be done with an
>>>XMLHttpRequest and a properly written webpage. This is a file that's
>>>going to be downloading over minutes/hours. We don't exactly need up
>>>to the second status updates, and even if we did, we can do that
>>>purely in the browser.
>>>
>>>
>>>There's UI tricks you could do to make it less difficult to check, if
>>>you really wanted to go that route. You could have a fproxy option to
>>>append a frame onto the side/top of all pages, similiar to the
>>>GoogleCache frame.
>>>I'm note sure of the feasibility, but couldn't the you feed one or two
>>>bits / second to the download, just enough to make it not time out?
>>>That way, when I click a link in fproxy, it starts a download, in my
>>>browser's exsiting download manager. Freenet continues to feed one or
>>>two bits of garbage/whitespace/whatever to the download every few
>>>seconds, to prevent a time out. From my perspective, it would look
>>>like any other download, just take a long time. When freenet
>>>internally finished downloading the file, it can just give the rest of
>>>the bits to the browser, which thinkgs it's been downloading the whole
>>>time.
>>>
>>>These are just examples, and not very good ones at that. But there's a
>>>lot of things that /could/ be done to make it feel like it belongs in
>>>a browser.
>>>
>>>Just a few random thoughts,
>>>Colin
>>>
>>>
>>>------------------------------------------------------------------------
>>>
>>>_______________________________________________
>>>Devl mailing list
>>>Devl at freenetproject.org
>>>http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
>>>
