(Special rate for the Six Figure Blogging course until Dec 2nd.)
« Google's loosing it's… | Home | » On Bloglines security…
Beat the Google Web Accelerator?
12.05.05 | filed in Tools, e
As far as I understand, the proxy catches all the files in advance. Can't I send a gzipped file to the other side?
A nice little 1k zipped file which blows up at the other side to 1 GB?
And before you tell me not so be so nasty - they should already have thought of that. :)
comments (2):
Phillip "molly" malone 12.05.05
I dare say that this idea wouldn’t work:
” Are there any files for which I can’t specify prefetching?
Yes, there are. We don’t prefetch HTTPS: files (i.e., secure pages), or large data files such as MP3 or MPEG. Note, however, that nothing bad will happen if you specify a file type which Google Web Accelerator doesn’t prefetch; that file type simply won’t load any faster.”
But nice try any way, but it looks like they have thought of it.
Molly
I dare say that this idea wouldn’t work:
” Are there any files for which I can’t specify prefetching?
Yes, there are. We don’t prefetch HTTPS: files (i.e., secure pages), or large data files such as MP3 or MPEG. Note, however, that nothing bad will happen if you specify a file type which Google Web Accelerator doesn’t prefetch; that file type simply won’t load any faster.”
But nice try any way, but it looks like they have thought of it.
Molly
Nicole 12.05.05
Sorry, I was not precise. You can let your web server deliver files gziped which are then unpacked at the other side. This speeds ups things for larger files.
Sorry, I was not precise. You can let your web server deliver files gziped which are then unpacked at the other side. This speeds ups things for larger files.
