On Thursday 27 March 2008 01:16, you wrote: > * Michael Rogers <m.rogers at cs.ucl.ac.uk> [2008-03-26 09:36:32]: > > > On Mar 25 2008, Matthew Toseland wrote: > > >Anyone got any better ideas? > > > > Sorry if this would be impossible, I don't know anything about fproxy's > > internals, but when a key is requested, would it be possible to display a > > "please wait" page with a "cancel" button and/or a link to the main fproxy > > page, then redirect to the content once it's been fetched? > > Sure it's possible... but not a realistic option. If the browser happens > to have reached its maximum amount of connections, I bet it won't obey > the "refresh" header we would set on the page we display, effectively > "breaking" the browsing.
Why would it be unrealistic? It wouldn't reach its maximum number of connections in the first place because connections wouldn't be blocked. The tricky bit is images - if they can't be loaded immediately, we might have to convert them to iframes or something. Which means we'd have to know how big they are. But if there are no dimensions specified? multipart/x-mixed-replace maybe, but some browsers may not support it? > > > It seems to me > > that people are opening lots of tabs, nothing is loading so they suspect > > Freenet has crashed, they try to open the stats page and when that fails it > > confirms their suspicion. So rather than changing Firefox, maybe we just > > need to give the user some feedback that Freenet is fetching the content > > and it hasn't crashed? > > I don't think it's why people open loads of tabs... Freenet's latency > sucks hence "parallelizing" makes sense -------------- 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/20080327/28675b7c/attachment.pgp>
