Name: Anonymous 2009-10-27 20:59
Has anyone considered setting up a local proxy server, vm or whatever, implementation isn't too critical... to cache certain requests? If you had a 100gb cache, that's a potentially huge speed-up.
Certain sites just would not work with the caching proxy due to needing a recent copy of the page, like 4chan. But, perhaps you could cache certain youtube videos / porn links that you tend to look at often. Instant loading ftw. Or, pre-emptive caching... load a certain page, and it will perform background requests to all links on that page in order to speed up browsing. Pre-emptively cache a page and all immediate subpages that your household might look at daily, for example, news sites. Could be handy for wikipedia as well, because chances are you might want to look at that article again.
Have every cached paged served up with a <div> on the top saying something like, "Cached on xx:xx:xx:xx, renew?" clicking on it would resend the request.
With the advent of huge amounts of storage space in your typical desktop (a new desktop these days could easily have 2TB), 100gb cache is not so bad. Bandwidth is typically not an issue. Use the LRU algorithm to detect which item to delete from the cache.
Of course, the only concern is that the increased web browsing traffic fucks up gaming. For this... 2 separate lines, one dedicated to real-time tasks (gaming, VOIP, email, etc), and the other dedicated to background network tasks (file transfer, web browsing)
If you're not rich (like most of us), have the proxy detect when someone is gaming and disable any pre-fetching.
What do you guys think?
Certain sites just would not work with the caching proxy due to needing a recent copy of the page, like 4chan. But, perhaps you could cache certain youtube videos / porn links that you tend to look at often. Instant loading ftw. Or, pre-emptive caching... load a certain page, and it will perform background requests to all links on that page in order to speed up browsing. Pre-emptively cache a page and all immediate subpages that your household might look at daily, for example, news sites. Could be handy for wikipedia as well, because chances are you might want to look at that article again.
Have every cached paged served up with a <div> on the top saying something like, "Cached on xx:xx:xx:xx, renew?" clicking on it would resend the request.
With the advent of huge amounts of storage space in your typical desktop (a new desktop these days could easily have 2TB), 100gb cache is not so bad. Bandwidth is typically not an issue. Use the LRU algorithm to detect which item to delete from the cache.
Of course, the only concern is that the increased web browsing traffic fucks up gaming. For this... 2 separate lines, one dedicated to real-time tasks (gaming, VOIP, email, etc), and the other dedicated to background network tasks (file transfer, web browsing)
If you're not rich (like most of us), have the proxy detect when someone is gaming and disable any pre-fetching.
What do you guys think?