> Am 2008-02-13 10:25:32, schrieb Matus UHLAR - fantomas: > > by using the same URI? or by different URI each time a song is requested? > > each of this makes problems with HTTP caching... On 14.02.08 09:58, Michelle Konzack wrote: > Yes, it is always the same url... > > For example: The original file is sampled in 192kBit and then a user > use: > > <http://musicserver/?rate=64&name=how_to_get_gnump3d_caching.mp3> either you are always fetching this URL and provide real arguments in POST requests (so I really don't know what are the rate= and name= for) or you missed that query strings are part of the URL, so different arguments mean different URL. And different URLs can (and will) be cached as different objects so we can benefit from caching (unless gnump3d disables caching somehow) -- Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. REALITY.SYS corrupted. Press any key to reboot Universe.
