On Friday 28 March 2008 00:28, Victor Denisov wrote: > I'm sorry if I missed something obvious, but why not use some simple JS > to handle this issue, polling Fproxy periodically with XHRs (possibly, > even showing progress bar, or something?) We're talking about using > "normal", untweaked browser here, correct? Well, about 95% of browsers > have JS enabled nowadays. And those who can and do turn off JS can > definitely tune their connection count as well.
Yes I suppose that's the other option. How exactly would this work? - For HTML, we simply send a we-are-still-loading page, with a Refresh header. - For inline images, the javascript would have to tell fproxy to start a fetch for each inline image. If any can be fetched immediately it could substitute them on the page. Then every few seconds it could poll all of them. This would probably be a significant drain on performance on something like FAI... > > Regards, > Victor Denisov. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20080328/50b16abc/attachment.pgp>
