If we're sure that what is connecting to us is a web browser, and the data is 
not in cache, we should show a loading screen when a user clicks on a link. 
With javascript this could be updated in real time, without it it could still 
be shown with a series of redirects.

ADVANTAGES:
- Reduce the level of user aggravation by showing them that something is 
happening.
- Possibly reduce the number of browser connections needed and thereby reduce 
the impact of running a non-optimised profile. (We WILL still need a custom 
browser profile however for security reasons).
- Look better.
- We could probably get rid of the 2MB stream-to-browser file size limit if a 
loading screen is displayed: We could just show the loading screen until the 
data is available and then send the whole lot to the user.

https://bugs.freenetproject.org/view.php?id=2781

Thoughts? Should this be a priority for 0.8? Does anyone want to implement it 
(I'm pretty busy atm!). Does anyone know Javascript well?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20081211/8c323cdd/attachment.pgp>

Reply via email to