"Niklas Bergh" <[EMAIL PROTECTED]> writes:
Now I believe I can live with freenet being slow and that many documents are not immediately available. What is annoying me is that _I_ will have to do the retrying. Why is that not a task for the server?
You sure? I thought we had a meta-refresh tag on those RNF/DNF pages? Wont the browser automatically retry the page after a while if you leave it to?
Hi again,
wanted to try Freenet again ;-) - seems to work quite well. However, those RNFs are really a PITA.
Yes, those RNF pages have meta refresh tags on them; however, that does not help if
a) one does not use Fproxy for fetching a file
b) the failing file is an image. In that case it just disappears and you have to reload the page manually until you have all images. (alternatively, you can open a browser window/tab for every single image you want to have; IMHO this is no real solution either.)
For me it seems as Fred is too fail-fast. It may try for a few more seconds or minutes instead of returning the RNF nearly immediately (and very often). Putting that retry to the user's side (being it the browser or a FCP app) is no good idea IMHO.
mihi
How would you distinguish messages you don't want very much (like possibly non-existent Frost messages) from ones you do want a lot? It is likely to generate quite a lot of extra traffic to automatically retry all RNFs till you get something, even if the user has gone on to something else. And that, of course, might lead to more RNFs, with obvious potential for regenerative feedback and massive overloading. There seems to be some indication for compromise here.
--
Roger Hayter
_______________________________________________
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]
