yeah, it is quite challenging to solve it correctly, but at least in the background vs. foreground case, we do have a fairly straightforward solution planned for sometime in the future. it is trivial to arrange our network queue to give higher priority to content in the focused window, for example. it may be a little more work to actually modulate background loads when there are active foreground loads, but i think it could be done fairly easily. the big problem as you state is conflicts between background downloads and prefetching. again, we'd have to have some way of prioritizing things to avoid killing off prefetch requests in certain cases. hmm...

darin



Alan Arndt wrote:

Darin,

Prefetching sounds wonderful, thanks for putting your time into it.

I have one comment that might be useful down the line.

When/if you are able to figure out proper idle time I would still like to be able to specify if the prefetch should take place. For instance now you place all other Mozilla activity above doing a prefetch. That seems reasonable, but it would be nice to choose that downloads are a lower priority. Quite frequently I have downloads running while I browse. That slows things down a bit, but I would still like the prefetch to be able to function once other tabbed pages are loaded.

I don�t know how or where the fact that some pages sit there waiting for thigns fits into this. If they are considered idle, great, if not that could be another issue. Some sites are just slow and it shouldn�t interfere with background loads.

It�s a challenging issue, good luck.

-Alan Arndt

[EMAIL PROTECTED]



Reply via email to